Skip site navigation (1) Skip section navigation (2)

Re: BUG #4899: Open parenthesis breaks query plan

From: "Peter Headland" <pheadland(at)actuate(dot)com>
To: "Greg Stark" <gsstark(at)mit(dot)edu>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4899: Open parenthesis breaks query plan
Date: 2009-07-06 17:35:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
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-----
From: gsstark(at)gmail(dot)com [mailto:gsstark(at)gmail(dot)com] On Behalf Of Greg
Sent: Monday, July 06, 2009 10:35
To: Peter Headland
Cc: Tom Lane; pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4899: Open parenthesis breaks query plan

On Mon, Jul 6, 2009 at 5:40 PM, Peter Headland<pheadland(at)actuate(dot)com>
> 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 depend on the c1/an_integer_column
value you're querying for than on the string. Keep trying different
values for both columns until you find one that triggers the problem
and send the explain analyze result for that. It could be that '(' was
such a value yesterday but not today if autovacuum has run analyze


In response to

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2009-07-06 17:53:28
Subject: Re: TH to_char modifier doesn't work with HH12
Previous:From: Greg StarkDate: 2009-07-06 17:35:13
Subject: Re: BUG #4899: Open parenthesis breaks query plan

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group