Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: thibaut(dot)madelaine(at)dalibo(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)
Date: 2019-03-05 15:39:07
Message-ID: 19353.1551800347@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> In PostgreSQL 10.7 and before, it is possible to run the following query:

> thibaut=# WITH test AS ( SELECT array[1,2] AS intarr )
> SELECT unnest(intarr) AS lot_id FROM test WHERE false;

> In version 11.2, the same query fails:
> ERROR: 0A000: set-valued function called in context that cannot accept a set

Hmm, that's definitely a bug. It looks like we're forgetting to make
a ProjectSet plan node for the unnest() if we realize that the query
is a no-op; but I'm not sure why 10.x doesn't have the same issue.
Digging ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Julien Rouhaud 2019-03-05 16:34:21 Re: BUG #15669: Error with unnest in PG 11 (ERROR: 0A000)
Previous Message Amit Langote 2019-03-05 15:16:10 Re: BUG #15670: alter table .. add column if not exists ... references ...; adds a FK constraint on each execution