MétaCan
Menu
Back to cohort
Record W2102820708 · doi:10.1109/apsec.2003.1254379

Implementing the PostgreSQL query optimizer within the OPT++ framework

2004· article· en· W2102820708 on OpenAlex
Ju Wang, Jinmiao Li, Gregory Butler

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Database Systems and Queries
Canadian institutionsConcordia University
Fundersnot available
KeywordsComputer scienceQuery optimizationSargableReuseSimple (philosophy)Code (set theory)Relational databaseQuery by ExampleQuery languageDatabaseWeb search queryInformation retrievalProgramming languageSearch engine

Abstract

fetched live from OpenAlex

Our work studies the application of an existing framework, called OPT++, for query optimization for relational databases. The initial application was a simple bottom-up optimizer, while the second application was to implement the query optimization strategies of PostgreSQL with the framework. Our experience illustrates the power and the pitfalls of reusing frameworks. During the course of the two applications we found substantial need to improve the design at the detailed level though the main abstractions of OPT++ did not change. Our second application raised many issues with the performance of OPT++, which is surprising since its fundamental purpose was a major study of relative performance of query optimization strategies by its author. We have addressed many performance issues, but some with broad impact on the framework's code are still being addressed.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.685
Threshold uncertainty score0.545

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.014
GPT teacher head0.269
Teacher spread0.255 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Quick stats

Citations2
Published2004
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Database Systems and QueriesFrench-language works237,207