| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Will Leinweber <will(at)bitfission(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Errors "failed to construct the join relation" and "failed to build any 2-way joins" |
| Date: | 2019-12-13 23:09:21 |
| Message-ID: | 13995.1576278561@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Will Leinweber <will(at)bitfission(dot)com> writes:
>> On 12.1, fresh initdb the following query gives me the error
>> "ERROR: failed to construct the join relation"
> Eyeing the plan produced by v11, I'm suspecting some oversight in
> the RTE_RESULT changes (4be058fe9); but I haven't actually bisected.
Yup: it's folding the join tree to the point where a PlaceHolderVar ends
up marked as to be evaluated by the same relation that uses it, and then
things go all pear-shaped. Here's a proposed patch for that.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| restrict-RESULT-RTE-removal-a-bit.patch | text/x-diff | 10.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-12-13 23:09:51 | Re: psql's \watch is broken |
| Previous Message | Justin Pryzby | 2019-12-13 22:47:35 | Re: error context for vacuum to include block number |