pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-19 17:37 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-21 23:49 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-22 12:12 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-22 12:37 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-23 03:43 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-23 17:51 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-24 02:43 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-24 06:22 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-25 04:29 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-26 00:09 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-28 07:01 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-28 17:37 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-29 06:06 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-30 05:30 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-09-30 07:48 UTC  John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-10-01 03:04 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-10-20 18:45 UTC  Greg Burd <greg@burd.me>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
  2026-10-22 03:22 UTC  Manu <manuelreyesbravo@gmail.com>
  [18+ messages in thread]

BUG #19787: "could not find pathkey item to sort" for Gather Merge over a merge join below reordered LEFT JOINs
  2026-10-21 22:37 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19785: Sorted GROUPING SETS return a grouping column's value in a set that leaves it out
  2026-10-21 22:11 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19785: Sorted GROUPING SETS return a grouping column's value in a set that leaves it out
  2026-10-21 22:19 UTC  Alperen Keleş <alpkeles99@gmail.com>
  [2+ messages in thread]

BUG #19773: pg_dump omits a different generation expression of an inherited column in a child table
  2026-10-20 02:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19773: pg_dump omits a different generation expression of an inherited column in a child table
  2026-10-21 18:39 UTC  Nitin Motiani <nitinmotiani@google.com>
  [2+ messages in thread]

BUG #19782: SET CONSTRAINTS in a released savepoint survives ROLLBACK TO an enclosing savepoint
  2026-10-21 18:25 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19781: UPDATE moving a row of a self-referencing partitioned table fails with 23503 although ON UPDATE CASC
  2026-10-21 18:23 UTC  PG Bug reporting form <noreply@postgresql.org>

Inconsistency in psql output with \d+x PATTERN
  2026-10-16 14:35 UTC  George MacKerron <george.mackerron@databricks.com>
` Re: Inconsistency in psql output with \d+x PATTERN
  2026-10-19 10:09 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: Inconsistency in psql output with \d+x PATTERN
  2026-10-19 11:34 UTC  George MacKerron <george.mackerron@databricks.com>
` Re: Inconsistency in psql output with \d+x PATTERN
  2026-10-19 16:07 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: Inconsistency in psql output with \d+x PATTERN
  2026-10-19 16:09 UTC  shihao zhong <zhong950419@gmail.com>
` Re: Inconsistency in psql output with \d+x PATTERN
  2026-10-19 16:10 UTC  shihao zhong <zhong950419@gmail.com>
` Re: Inconsistency in psql output with \d+x PATTERN
  2026-10-21 14:47 UTC  Fujii Masao <masao.fujii@gmail.com>
  [7+ messages in thread]

BUG #19770: CREATE TABLE (LIKE ...) PARTITION BY copies a NO INHERIT not-null constraint; NULLs then go into par
  2026-10-18 13:58 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19770: CREATE TABLE (LIKE ...) PARTITION BY copies a NO INHERIT not-null constraint; NULLs then go into par
  2026-10-21 08:34 UTC  Nitin Motiani <nitinmotiani@google.com>
  [2+ messages in thread]

BUG #19771: to_char(): NUL byte in result for formats with a trailing decimal point (regression from ec352b37d)
  2026-10-18 20:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19771: to_char(): NUL byte in result for formats with a trailing decimal point (regression from ec352b37d)
  2026-10-18 20:47 UTC  Gowtham Reddy <gowthamdoma18@gmail.com>
` Re: BUG #19771: to_char(): NUL byte in result for formats with a trailing decimal point (regression from ec352b37d)
  2026-10-19 00:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19771: to_char(): NUL byte in result for formats with a trailing decimal point (regression from ec352b37d)
  2026-10-20 17:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19771: to_char(): NUL byte in result for formats with a trailing decimal point (regression from ec352b37d)
  2026-10-20 18:52 UTC  Gowtham Reddy <gowthamdoma18@gmail.com>
  [5+ messages in thread]

Bug in statement trigger for MERGE operations that move rows between partitions
  2026-10-08 22:44 UTC  Michael Ries <mries@salesforce.com>
` Re: Bug in statement trigger for MERGE operations that move rows between partitions
  2026-10-20 15:36 UTC  Michael Ries <mries@salesforce.com>
  [2+ messages in thread]

GIN (JSONPath) checks equality only on the first node of each operand
  2026-10-11 02:04 UTC  Chinmay Kanchi <cgkanchi@gmail.com>
` Re: GIN (JSONPath) checks equality only on the first node of each operand
  2026-10-11 18:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: GIN (JSONPath) checks equality only on the first node of each operand
  2026-10-20 06:59 UTC  Rui Zhao <zhaorui126@gmail.com>
  [3+ messages in thread]

BUG #19769: int8range() raises an error for an inclusive upper bound at BIGINT_MAX
  2026-10-18 11:59 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19769: int8range() raises an error for an inclusive upper bound at BIGINT_MAX
  2026-10-19 16:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

use-after-free in jsonb_set_lax()
  2026-10-15 02:44 UTC  John Naylor <johncnaylorls@gmail.com>
` Re: use-after-free in jsonb_set_lax()
  2026-10-15 04:08 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: use-after-free in jsonb_set_lax()
  2026-10-15 05:31 UTC  John Naylor <johncnaylorls@gmail.com>
` Re: use-after-free in jsonb_set_lax()
  2026-10-15 06:21 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: use-after-free in jsonb_set_lax()
  2026-10-15 09:08 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: use-after-free in jsonb_set_lax()
  2026-10-16 02:23 UTC  John Naylor <johncnaylorls@gmail.com>
` Re: use-after-free in jsonb_set_lax()
  2026-10-16 03:28 UTC  Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
` Re: use-after-free in jsonb_set_lax()
  2026-10-19 05:02 UTC  John Naylor <johncnaylorls@gmail.com>
  [8+ messages in thread]

BUG #19766: Assert in shm_toc_insert: EXPLAIN ANALYZE of a SubPlan shared by Parallel Append children
  2026-10-16 15:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19766: Assert in shm_toc_insert: EXPLAIN ANALYZE of a SubPlan shared by Parallel Append children
  2026-10-18 01:23 UTC  BHUVAN CHILUKUTI <c.bhuvan@iitg.ac.in>
  [2+ messages in thread]

ANALYZE-generated NaN range lengths cause 1e100-row estimates
  2026-10-17 16:18 UTC  rh@vonng.com

BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb post-bootstrap subprocess
  2026-10-15 15:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb post-bootstrap subprocess
  2026-10-15 16:34 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb post-bootstrap subprocess
  2026-10-15 19:36 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb post-bootstrap subprocess
  2026-10-16 04:00 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb
  2026-10-17 07:05 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb
  2026-10-17 08:48 UTC  violin <1217816127@qq.com>
` Re: BUG #19764: ManualBug3 Assert failure in pgstat_setup_shared_refs crashes initdb
  2026-10-17 09:03 UTC  Manu <manuelreyesbravo@gmail.com>
  [7+ messages in thread]

reltuples kept decreasing with each autovacuum run Re: BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
  2025-01-15 16:53 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
  2025-01-21 07:45 UTC  Michael Paquier <michael@paquier.xyz>
`  Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773: オートバキュームのリトライ時にreltuplesの値が減少する
  2025-01-29 02:16 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773
  2026-10-16 17:09 UTC  Michael Banck <mbanck@gmx.net>
  [4+ messages in thread]

BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-19 11:06 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-20 04:37 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-20 10:03 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-20 11:31 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-20 12:05 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-20 12:45 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-21 08:10 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-21 11:31 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-21 11:48 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-05-25 08:53 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-10-09 04:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-10-09 04:53 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-10-15 02:55 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
  2026-10-16 15:22 UTC  Fujii Masao <masao.fujii@gmail.com>
  [14+ messages in thread]

Volatile expressions in SQL/JSON functions are evaluated twice
  2026-10-16 10:56 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>

BUG #19762: ManualBug1 tcn: NULL pointer dereference in triggered_change_notification() via strcpy_quoted
  2026-10-15 15:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19762: ManualBug1 tcn: NULL pointer dereference in triggered_change_notification() via strcpy_quoted
  2026-10-15 16:14 UTC  Tomas Vondra <tomas@vondra.me>
  [2+ messages in thread]

BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
  2026-09-07 14:06 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
  2026-09-26 15:25 UTC  Rahul Yadav <rahul@rhyadav.com>
` Re: BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
  2026-09-27 17:57 UTC  Andrew Krylosov <krylosov.andrew@gmail.com>
` Re: BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
  2026-10-15 06:29 UTC  solai v <solai.cdac@gmail.com>
  [4+ messages in thread]

BUG #19755: Server-wide hang: DROP DATABASE waits forever for ProcSignalBarrier while VACUUM waits on pg_databas
  2026-10-12 12:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19755: Server-wide hang: DROP DATABASE waits forever for ProcSignalBarrier while VACUUM waits on pg_databas
  2026-10-15 04:31 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-01 14:27 UTC  Vladimir Savin <vladimir@encord.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-01 16:15 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-01 19:36 UTC  Vladimir Savin <vladimir@encord.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-02 08:04 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-02 08:12 UTC  Vladimir Savin <vladimir@encord.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-08 08:08 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-08 08:30 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-08 22:04 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-09 14:28 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-10 11:51 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-12 00:16 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-15 00:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-15 01:25 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
  2026-10-15 02:53 UTC  David Rowley <dgrowleyml@gmail.com>
  [14+ messages in thread]

BUG #19758: Nested BETWEEN grows time and space exponentially in parse analysis
  2026-10-14 17:12 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19757: attname in pg_attribute not strictly updated when renaming a column
  2026-10-14 14:04 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19757: attname in pg_attribute not strictly updated when renaming a column
  2026-10-14 15:02 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