Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: BUG #19735: `jsonb_object_agg_unique_strict` drops a JSONB `null`
 value as if it were SQL NULL
To: pgsql-bugs@lists.postgresql.org
From: PG Bug reporting form <noreply@postgresql.org>
Cc: theshallow27@gmail.com
Reply-To: theshallow27@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Fri, 02 Oct 2026 22:03:41 +0000
Message-ID: <19735-488819822dc79bca@postgresql.org>
Auto-Submitted: auto-generated
Archived-At: 
 <https://www.postgresql.org/message-id/19735-488819822dc79bca%40postgresql.org>
Precedence: bulk

The following bug has been logged on the website:

Bug reference:      19735
Logged by:          Shallow
Email address:      theshallow27@gmail.com
PostgreSQL version: 18.6
Operating system:   Linux
Description:       =20

The strict JSONB object aggregate omits a non-SQL-NULL `jsonb` datum whose
JSON
value is `null`. The corresponding non-strict JSONB aggregate and strict
JSON
aggregate preserve the key with a JSON null value. The aggregate
documentation
says that strict mode skips a value when the value is NULL; a JSONB `null`
value
is distinct from SQL NULL.

**Reproduction:**

```sql
SELECT jsonb_object_agg_unique_strict('a', 'null'::jsonb)::text,
       jsonb_object_agg_unique('a', 'null'::jsonb)::text,
       json_object_agg_unique_strict('a', 'null'::jsonb)::text;
```

**Actual result:**

```text
{} | {"a": null} | { "a" : null }
```

**Expected result:** The strict JSONB aggregate should skip SQL NULL values
but
preserve a JSONB datum containing JSON `null`, consistent with the other two
aggregate results.