The following bug has been logged online:
Bug reference: 4899
Logged by: Peter Headland
Email address: pheadl...@actuate.com
PostgreSQL version: 8.4.0
Operating system: Windows
Description:Open parenthesis breaks query plan
Details:
In a moderate-size table
The following bug has been logged online:
Bug reference: 4900
Logged by: Peter Headland
Email address: pheadl...@actuate.com
PostgreSQL version: 8.4.0
Operating system: Windows
Description:Query planner misses obvious optimization on ordered
UNION DISTINCT
Details
shandling parentheses. I don't understand why
parentheses should be significant inside a string literal in the first place.
Also, just to be 100% clear, the open paren can be anywhere in the string, so a
comparison to 'abcdefgh(ijklmnop' still triggers the bug.
--
Peter Headl
ans is that the initial symbol with the name of the
index underneath vanishes when there is an unmatched open parenthesis. I
have been unable to find an explanation of the symbols used in pgAdmin
III - is there such a thing anywhere?
If we are agreed that the issue is a bug in pgAdmin III, please a
As I said further down my previous e-mail, it looks as if the optimizer
is just fine, and the problem is simply a bug in the way pgAdmin III
parses and displays EXPLAIN ANALYZE output in its graphical view.
--
Peter Headland
Architect - e.Reports
Actuate Corporation
-Original Message
