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-
F
On Mon, Jul 6, 2009 at 5:40 PM, Peter Headland wrote:
> presence
> of a '(' character anywhere at all in the string literal triggers the
> problem. For example 'abc(def'.
Except according to that explain analyze 'abc(def' ran exactly the
speed as 'abc()def'.
This all seems much more likely to dep
dvise
where I should report such things.
--
Peter Headland
Architect - e.Reports
Actuate Corporation
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Sunday, July 05, 2009 08:39
To: Peter Headland
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4899: Op
"Peter Headland" writes:
> While noodling around some more, I found that a comparison to '()'
> allows use of the index, as does '(abc)' and even '(a(b(c)d)e)'. It
> appears that mismatched open/close paren pairs trigger the
> bug. Obviously something is parsing the string literal and mishandling
On Sunday 05 July 2009 03:03:00 Peter Headland wrote:
> 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 parent
While noodling around some more, I found that a comparison to '()' allows use
of the index, as does '(abc)' and even '(a(b(c)d)e)'. It appears that
mismatched open/close paren pairs trigger the bug. Obviously something is
parsing the string literal and mishandling parentheses. I don't understand
