From: Tom Lane <tgl@sss.pgh.pa.us>
To: kleptog@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17564: Planner bug in combination of generate_series(),
 unnest() and ORDER BY
In-reply-to: <17564-c7472c2f90ef2da3@postgresql.org>
References: <17564-c7472c2f90ef2da3@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 01 Aug 2022 14:54:30 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2184334.1659392231.1@sss.pgh.pa.us>
Date: Mon, 01 Aug 2022 18:17:11 -0400
Message-ID: <2184335.1659392231@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2184335.1659392231%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> db=# explain SELECT generate_subscripts(ARRAY[]::integer[], 1) AS id, 
>        unnest(ARRAY[]::jsonb[]) ->> 'timestamp'  AS timestamp 
> FROM results 
> JOIN groups ON groups.id = results.group_id 
> WHERE results.search_id = 3336 
> order by timestamp;

> The error is:

> ERROR:  set-valued function called in context that cannot accept a set
> LINE 2:        unnest(ARRAY[]::jsonb[]) ->> 'timestamp'  AS timestam...

Hmm, that certainly seems like a bug, but I fear it's impossible
to investigate without a reproducible test case.

			regards, tom lane