filter with json_agg(DISTINCT table.*) behaves differently

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: mihirpmehta(at)gmail(dot)com
Subject: filter with json_agg(DISTINCT table.*) behaves differently
Date: 2020-04-22 10:11:22
Message-ID: 158755028255.635.4092609317677999644@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/release-10-7.html
Description:

Following is our finding:

Postgres query behaves differently in 2 version

Specifically

(json_agg(DISTINCT table_name.*) filter(where table_name is not null)) as
table,
.
.
.

gives null record in 10.7 where it gives proper data in 10.6

Following is the version difference of postgres

WORKING - PostgreSQL 10.6 on x86_64-pc-linux-gnu, compiled by gcc (GCC)
4.8.3 20140911 (Red Hat 4.8.3-9), 64-bit

NOT WORKING - PostgreSQL 10.7 on x86_64-pc-linux-gnu, compiled by gcc (GCC)
4.9.3, 64-bit

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2020-04-22 15:29:36 Add that changing the `argname` will raise exception in procedure/function
Previous Message Rui Hai Jiang 2020-04-22 07:52:39 Document format issues: characters are overlapping in the header of some tables