From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Poot, Bas (B.J.)" <bas.poot@politie.nl>
cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: subselect removes rows
In-reply-to: <57ceecb9c50743eeaf8732fcf2185d68@politie.nl>
References: 
 <a5ed0b646f2e465d90954fa79d5837b5@politie.nl>,<1217100.1638198095@sss.pgh.pa.us>
 <57ceecb9c50743eeaf8732fcf2185d68@politie.nl>
Comments: In-reply-to "Poot, Bas (B.J.)" <bas.poot@politie.nl>
	message dated "Mon, 29 Nov 2021 15:44:54 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1268250.1638207288.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2021 12:34:48 -0500
Message-ID: <1268251.1638207288@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1268251.1638207288%40sss.pgh.pa.us>
Precedence: bulk

"Poot, Bas (B.J.)" <bas.poot@politie.nl> writes:
> The problem is that I don't expect (and can't imagine it is correct) tha=
t a (any) sub-select removes rows from the resultset.

I'm really not sure what you're saying here.  If you're complaining
about jsonb_each_text returning no rows for empty input, that behavior
hasn't changed, and it's hard to see what else it could do.  Your
example isn't showing any other behavior that seems odd.

			regards, tom lane