> -----Original Message----- > From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general- > owner@xxxxxxxxxxxxxx] On Behalf Of Tom Lane > Sent: Dienstag, 13. Dezember 2016 16:32 > To: Torsten Förtsch > Cc: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: is this a known bug in 9.6? > > =?UTF-8?Q?Torsten_F=C3=B6rtsch?= <tfoertsch123@xxxxxxxxx> writes: > > postgres=# with i(x) as (values (1::int)), j(y) as (values (2::int)) > > select x from (select x from i union all select y from j) b; x > > --- > > 1 > > 2 > > (2 rows) > > > postgres=# with i(x) as (values (1::int)), j(y) as (values (2::int)) > > select > > max(x) from (select x from i union all select y from j) b; > > ERROR: could not find plan for CTE "i" > > Yup, sure looks like a bug to me, especially since it seems to work as > expected before 9.5. No idea offhand what broke it. > > regards, tom lane This is strange: using another aggreg. function works: with i as (select 1::int x), j as (select 1::int x) select count(x) from (select x from i union all select x from j) b; --- 2 with i as (select 1::int x), j as (select 1::int x) select max(x) from (select x from i union all select x from j) b; --- ERROR: could not find plan for CTE "i" regards, Marc Mamin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
