| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | bgrundmann(at)janestreet(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14111: After minor upgrade (9.2.6 -> 9.2.16): ERROR: failed to build any 2-way joins |
| Date: | 2016-04-25 16:14:11 |
| Message-ID: | CAKFQuwaU-LZyWsNSqBi0ripB+=MQS6zMdAroasNRhZsjisOmCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Apr 25, 2016 at 5:03 AM, <bgrundmann(at)janestreet(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14111
> Logged by: Benedikt Grundmann
> Email address: bgrundmann(at)janestreet(dot)com
> PostgreSQL version: 9.2.16
> Operating system: Linux
> Description:
>
> >From all I know so far we have a query that used to work last week and
> after
> upgrading from 9.2.6 to 9.2.16 this weekend, we get
>
> ERROR: failed to build any 2-way joins
>
> when trying to plan the same query (that is either run the query or even
> just explain it). The query is this:
>
>
This sounds like the same as bug #
14105
http://www.postgresql.org/message-id/20160420194758.22924.80319@wrigleys.postgresql.org
That one has been corrected and will go out in the next release.
http://git.postgresql.org/pg/commitdiff/d9742ac4636ec847f9fd54c9d690da
7402319063
Someone with source compilation can hopefully confirm that your specific
example is indeed fixed.
The combinations of left and full join lead me to suspect that indeed these
are caused by the same bug.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-04-25 16:38:36 | Re: [BUGS] Breakage with VACUUM ANALYSE + partitions |
| Previous Message | Andres Freund | 2016-04-25 15:56:27 | Re: [BUGS] Breakage with VACUUM ANALYSE + partitions |