| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | magnus(dot)falch(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17340: Unnest discards rows with empty or null arrays |
| Date: | 2021-12-22 20:43:49 |
| Message-ID: | CAKFQuwaNHjCR1C4efXWfGKBcW-8_0sOesACdvbUHiD4NSf-Uaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Dec 20, 2021 at 3:42 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17340
> Logged by: Magnus Falch
> Email address: magnus(dot)falch(at)gmail(dot)com
> PostgreSQL version: 14.1
> Operating system: Ubuntu 20.04
> Description:
>
> No part of the documentation covers this behaviour
Yes, this is under-documented.
and it feels incorrect.
>
That may be, but this is how it works. Placing any set-returning function
call directly in the select target list performs an INNER JOIN. The
LATERAL JOIN feature was added to allow the user more flexibility - the
syntax you are complaining about should be considered obsolete.
While this hasn't been complained about in a while you are the second to
question it in the past month or so:
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-12-22 20:48:12 | Re: BUG #17340: Unnest discards rows with empty or null arrays |
| Previous Message | Bruce Momjian | 2021-12-22 20:31:58 | Re: BUG #17340: Unnest discards rows with empty or null arrays |