From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | ERROR: cannot handle unplanned sub-select |
Date: | 2010-07-06 16:00:43 |
Message-ID: | AANLkTikcGAOq2eHCU0fq7rdljLNlgxrvJfw99ujwds_D@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Not 100% sure I have a bug, but I've never seen this before so I
though it was worth a post. Confirmed on 8.4.4 and 9.0 beta. I have
a small self contained test case that I can send off line or on the
list following some code obfuscation (it's fairly complex to set up).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Ranga Gopalan | 2010-07-06 18:20:06 | BUG #5543: Poor performance - Index scan backwards not used for order by desc with partitioned tables |
Previous Message | Dimitri Fontaine | 2010-07-06 08:16:41 | Re: BUG #5532: Valid UTF8 sequence errors as invalid |
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Cousin | 2010-07-06 16:35:06 | Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore |
Previous Message | Robert Haas | 2010-07-06 15:29:38 | Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes. |