Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimizer chooses slower PLAN in v2.0.5/v2.1.2 than in v2.0.4/v2.1.1 [CORE2411] #2829

Closed
firebird-issue-importer opened this issue Apr 8, 2009 · 14 comments

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2009

Submitted by: Dejan Schild (schild)

Relate to CORE2488
Is related to QA249

Attachments:
DEBUG.zip

In FB 2.1.2, with some queries I got much slower execution than with 2.1.1. After some investigation, I found that optimizer choose different plan, that is up to 4x slower. I made test database, and here is simple test statement. Maybe something with CORE2078?

select d.uid
from promene_doc p
inner join dokumenti d on (p.prom_uid = d.uid)
inner join tipovi_vrste v on (v.tipvrsta=d.tipvrsta)
where (d.op=2) and (d.stornodok=0)

-- fast 2.1.1 --PLAN JOIN (P NATURAL, D INDEX (DOKUMENTI_PK), V INDEX (TIPOVI_VRSTE_PK))
-- slow 2.1.2 --PLAN JOIN (V NATURAL, D INDEX (FK_DOK_TIPVRSTA), P INDEX (PK_PROMENE_DOC))

Commits: a7b6702 a082a6f 4b79215

====== Test Details ======

Broken link to attachment.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2009

Commented by: Dejan Schild (schild)

Test database

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2009

Modified by: Dejan Schild (schild)

Attachment: DEBUG.zip [ 11434 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2009

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2009

Modified by: @dyemanov

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 14, 2009

Modified by: @dyemanov

status: In Progress [ 3 ] => Open [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 14, 2009

Commented by: @dyemanov

This issue should be fixed now. You may test it with the next (tomorrow's) snapshot builds.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 14, 2009

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10300 ]

Fix Version: 2.1.3 [ 10302 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 14, 2009

Modified by: @dyemanov

Fix Version: 2.0.6 [ 10303 ]

summary: Optimizer choose slower PLAN in v.2.1.2 than in v.2.1.1 => Optimizer chooses slower PLAN in v2.0.5/v2.1.2 than in v2.0.4/v2.1.1

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 14, 2009

Modified by: @dyemanov

Version: 2.0.5 [ 10222 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 3, 2009

Modified by: @dyemanov

Link: This issue relate to CORE2488 [ CORE2488 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 23, 2011

Modified by: @pcisar

Link: This issue is related to QA249 [ QA249 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 31, 2011

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 18, 2016

Modified by: @pavel-zotov

QA Status: No test

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 7, 2016

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Test Details: Broken link to attachment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants