pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-09-18 02:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-09-18 15:03 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-09-19 00:58 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-09-23 20:12 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-09-24 17:03 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-09-24 20:49 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
  2026-11-05 03:41 UTC  Amit Langote <amitlangote09@gmail.com>
  [7+ messages in thread]

Wrong result: count(DISTINCT x COLLATE "C") with GROUP BY x on a nondeterministic collation
  2026-11-01 09:27 UTC  Nidal FAKIH <nidal.fakih@soptimal.com>
` Re: Wrong result: count(DISTINCT x COLLATE "C") with GROUP BY x on a nondeterministic collation
  2026-11-04 09:34 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Wrong result: count(DISTINCT x COLLATE "C") with GROUP BY x on a nondeterministic collation
  2026-11-04 21:33 UTC  David Rowley <dgrowleyml@gmail.com>
  [3+ messages in thread]

BUG #19830: Mention that UNIQUE on a nondeterministic ICU collation treats ignorable characters as duplicates
  2026-11-04 01:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19830: Mention that UNIQUE on a nondeterministic ICU collation treats ignorable characters as duplicates
  2026-11-04 13:46 UTC  Peter Eisentraut <peter@eisentraut.org>
  [2+ messages in thread]

BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-02 15:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-02 16:08 UTC  Robins Tharakan <tharakan@gmail.com>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-03 01:14 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-03 03:39 UTC  Robins Tharakan <tharakan@gmail.com>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-03 11:22 UTC  Robins Tharakan <tharakan@gmail.com>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-03 12:45 UTC  Robins Tharakan <tharakan@gmail.com>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-04 03:25 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-04 10:15 UTC  Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19827: postgres_fdw: Assert in add_foreign_ordered_paths() with redundant ORDER BY in set-op input
  2026-11-04 11:30 UTC  Robins Tharakan <tharakan@gmail.com>
  [9+ messages in thread]

Incorrect NOT IN results with implicit casts returning NULL after anti-join optimization
  2026-10-23 18:04 UTC  BHUVAN CHILUKUTI <c.bhuvan@iitg.ac.in>
` Re: Incorrect NOT IN results with implicit casts returning NULL after anti-join optimization
  2026-11-01 03:15 UTC  shihao zhong <zhong950419@gmail.com>
` Re: Incorrect NOT IN results with implicit casts returning NULL after anti-join optimization
  2026-11-01 03:37 UTC  BHUVAN CHILUKUTI <c.bhuvan@iitg.ac.in>
` Re: Incorrect NOT IN results with implicit casts returning NULL after anti-join optimization
  2026-11-04 07:47 UTC  Richard Guo <guofenglinux@gmail.com>
  [4+ messages in thread]

BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-09-25 19:38 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-09-26 09:02 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-09-26 09:31 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-09-26 14:26 UTC  Nate Clark <natec425@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-10-02 18:20 UTC  Nate Clark <natec425@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-10-05 03:37 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-11-03 09:32 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-11-03 10:35 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
  2026-11-04 02:27 UTC  Fujii Masao <masao.fujii@gmail.com>
  [9+ messages in thread]

BUG #19594: to_char/jsonpath format cache serves a format tree parsed in the wrong strict-mode
  2026-08-01 15:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19594: to_char/jsonpath format cache serves a format tree parsed in the wrong strict-mode
  2026-08-01 16:50 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19594: to_char/jsonpath format cache serves a format tree parsed in the wrong strict-mode
  2026-11-03 13:39 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19594: to_char/jsonpath format cache serves a format tree parsed in the wrong strict-mode
  2026-11-03 13:42 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [4+ messages in thread]

BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-10-29 15:32 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-10-30 19:10 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-10-30 19:47 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-10-30 19:59 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-10-30 21:36 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-10-31 00:28 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
  2026-11-03 12:53 UTC  Daniel Gustafsson <daniel@yesql.se>
  [7+ messages in thread]

Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-10-01 18:29 UTC  Samuel Olaoye <dapsalmy@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-10-02 07:47 UTC  rahul@rhyadav.dev
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-10-16 23:26 UTC  Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-10-17 12:05 UTC  Rahul <rahul@rhyadav.dev>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-10-30 07:24 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-10-31 04:49 UTC  shihao zhong <zhong950419@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-11-02 05:51 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-11-02 07:06 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
  2026-11-03 08:39 UTC  Rahul <rahul@rhyadav.dev>
  [9+ messages in thread]

BUG #19829: BTREE pivot tuple length overflows t_info when BLCKSZ=32768
  2026-11-03 07:46 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19829: BTREE pivot tuple length overflows t_info when BLCKSZ=32768
  2026-11-03 08:10 UTC  王飞 <wf13934952799@gmail.com>
` Re: BUG #19829: BTREE pivot tuple length overflows t_info when BLCKSZ=32768
  2026-11-03 08:12 UTC  王飞 <wf13934952799@gmail.com>
  [3+ messages in thread]

ORCE ROW LEVEL SECURITY makes ADD/VALIDATE FOREIGN KEY skip rows hidden from the owner (RI_Initial_Check)
  2026-10-25 09:34 UTC  Ludwig Kannicht <info@luline.de>
` Re: ORCE ROW LEVEL SECURITY makes ADD/VALIDATE FOREIGN KEY skip rows hidden from the owner (RI_Initial_Check)
  2026-11-03 03:49 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

data race in libpq process-global variables (static_client_encoding / static_std_strings) when connections are established concurrently
  2026-10-21 13:44 UTC  Yuriy Osadchyy <yuriy_osadchyy@trimble.com>
` Re: data race in libpq process-global variables (static_client_encoding / static_std_strings) when connections are established concurrently
  2026-11-03 03:29 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-09-28 03:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-10-04 09:51 UTC  weijie JL <weijie1006jl@gmail.com>
` Re: BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-10-21 17:44 UTC  Dmytro Astapov <dastapov@gmail.com>
` Re: BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-10-23 07:15 UTC  weijie JL <weijie1006jl@gmail.com>
` Re: BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-10-24 12:07 UTC  Dmytro Astapov <dastapov@gmail.com>
` Re: BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-11-03 01:08 UTC  Dmytro Astapov <dastapov@gmail.com>
` Re: BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
  2026-11-03 01:22 UTC  weijie JL <weijie1006jl@gmail.com>
  [7+ messages in thread]

BUG #19828: "plan should not reference subplan's variable" with Memoize since f8da64e6
  2026-11-02 16:06 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19828: "plan should not reference subplan's variable" with Memoize since f8da64e6
  2026-11-02 16:08 UTC  Venu K <venu2805k@gmail.com>
  [2+ messages in thread]

Server crash on UPDATE after savepoint rollback when the row is locked by the same transaction (Assert HEAP_XMAX_IS_LOCKED_ONLY in heap_update)
  2026-11-02 07:14 UTC  RekGRpth <rekgrpth@gmail.com>
` Re: Server crash on UPDATE after savepoint rollback when the row is locked by the same transaction (Assert HEAP_XMAX_IS_LOCKED_ONLY in heap_update)
  2026-11-02 08:51 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Server crash on UPDATE after savepoint rollback when the row is locked by the same transaction (Assert HEAP_XMAX_IS_LOCKED_ONLY in heap_update)
  2026-11-02 09:36 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
  [3+ messages in thread]

contrib/cube: NaN coordinates break the btree equivalence relation, so UNIQUE rejects distinct values and ORDER BY is unstable
  2026-11-02 09:06 UTC  apex-security-research <apex-security-research@proton.me>

BUG #19408: Bad plan for UNION ALL subquery with outer WHERE, ORDER BY, LIMIT, and separate indexes
  2026-02-13 19:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19408: Bad plan for UNION ALL subquery with outer WHERE, ORDER BY, LIMIT, and separate indexes
  2026-02-13 23:36 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19408: Bad plan for UNION ALL subquery with outer WHERE, ORDER BY, LIMIT, and separate indexes
  2026-11-02 05:19 UTC  shihao zhong <zhong950419@gmail.com>
  [3+ messages in thread]

BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-10-24 22:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-10-25 15:31 UTC  Zhijie Hou <houzhijie22@gmail.com>
` RE: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-10-26 02:56 UTC  Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-10-27 17:36 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-10-31 11:31 UTC  Zhijie Hou <houzhijie22@gmail.com>
` Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-10-31 11:32 UTC  Zhijie Hou <houzhijie22@gmail.com>
` Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-11-01 08:00 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
  2026-11-01 23:15 UTC  Michael Paquier <michael@paquier.xyz>
  [8+ messages in thread]

BUG #19774: Incremental backup loses re-extended blocks when WAL summaries are merged out of LSN order
  2026-10-20 03:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19774: Incremental backup loses re-extended blocks when WAL summaries are merged out of LSN order
  2026-10-21 08:17 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19774: Incremental backup loses re-extended blocks when WAL summaries are merged out of LSN order
  2026-10-21 10:03 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19774: Incremental backup loses re-extended blocks when WAL summaries are merged out of LSN order
  2026-10-22 08:48 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19774: Incremental backup loses re-extended blocks when WAL summaries are merged out of LSN order
  2026-11-01 15:31 UTC  Fujii Masao <masao.fujii@gmail.com>
  [5+ messages in thread]

BUG #19825: JSON_VALUE(... RETURNING <domain over json/jsonb>) loses the re-quoting of scalar strings and silent
  2026-11-01 14:40 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19824: OMIT QUOTES breaks non-string results: array / composite / array-domain coercions in JSON_QUERY / JS
  2026-11-01 08:07 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19823: JSON_VALUE(... RETURNING jsonb) silently returns NULL for PASSING values of NaN / Infinity; the expo
  2026-11-01 08:06 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19814: pg_restore_attribute_stats: MCV accepted without eq operator; ANALYZE range slot rejected
  2026-10-29 07:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19814: pg_restore_attribute_stats: MCV accepted without eq operator; ANALYZE range slot rejected
  2026-10-31 00:26 UTC  Michael Paquier <michael@paquier.xyz>
  [2+ messages in thread]

BUG #19821: pg_restore_attribute_stats() accepts an unsorted scalar histogram_bounds, producing badly wrong row
  2026-10-30 07:01 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19821: pg_restore_attribute_stats() accepts an unsorted scalar histogram_bounds, producing badly wrong row
  2026-10-30 09:50 UTC  mingjie gao <mingjie.gmj@gmail.com>
` Re: BUG #19821: pg_restore_attribute_stats() accepts an unsorted scalar histogram_bounds, producing badly wrong row
  2026-10-31 00:19 UTC  Michael Paquier <michael@paquier.xyz>
  [3+ messages in thread]

BUG #19809: oidvector index dedup still returns wrong results on 18.6; CTAS persists the corrupted rows
  2026-10-29 06:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19809: oidvector index dedup still returns wrong results on 18.6; CTAS persists the corrupted rows
  2026-10-30 21:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]


[next (older)]

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox