| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Peter Headland <pheadland(at)actuate(dot)com> |
| 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:13 |
| Message-ID: | 407d949e0907061035g614250akb1c9c61b1d68be85@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jul 6, 2009 at 5:40 PM, Peter Headland<pheadland(at)actuate(dot)com> 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 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
since.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Headland | 2009-07-06 17:35:19 | Re: BUG #4899: Open parenthesis breaks query plan |
| Previous Message | Tom Lane | 2009-07-06 16:43:18 | Re: TH to_char modifier doesn't work with HH12 |