From: Tom Lane <tgl@sss.pgh.pa.us>
To: Elvis Pranskevichus <elprans@gmail.com>
cc: pgsql-bugs@postgresql.org
Subject: Re: ERROR: could not devise a query plan for the given query (UNIONS
 and LATERAL)
In-reply-to: <5981018.zdth1YWmNy@hammer.magicstack.net>
References: <5981018.zdth1YWmNy@hammer.magicstack.net>
Comments: In-reply-to Elvis Pranskevichus <elprans@gmail.com>
	message dated "Tue, 23 Jan 2018 13:10:59 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26532.1516738777.1@sss.pgh.pa.us>
Date: Tue, 23 Jan 2018 15:19:37 -0500
Message-ID: <26533.1516738777@sss.pgh.pa.us>
Precedence: bulk

Elvis Pranskevichus <elprans@gmail.com> writes:
> The following (admittedly bizzare) query causes the error in the subject 
> on all recent versions of Postgres:

Interesting.  What this shows is that reparameterize_path has to be able
to work on an AppendPath, because if you've got nested appendrels that's
the only sort of path there will be for that particular child of the
outer appendrel.

I'm a little worried about whether this doesn't mean that
reparameterize_path needs to be able to work on any kind of path.
However, given that it's been there quite some time without previous
reports of trouble, jumping to that conclusion may be premature.

I'm also wondering where reparameterize_path_by_child came from and
why it's so enormously more ambitious than reparameterize_path
in terms of its path-type coverage.

			regards, tom lane