pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Possible G2-item at SERIALIZABLE
  2026-05-22 16:44 UTC  Kyle Kingsbury <aphyr@aphyr.com>
` Re: Possible G2-item at SERIALIZABLE
  2026-05-30 18:47 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-05-31 13:19 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-01 01:49 UTC  Kyle Kingsbury <aphyr@jepsen.io>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-01 06:18 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-01 10:11 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-01 22:00 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-02 08:18 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-02 23:03 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
  2026-06-17 17:39 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-08-19 17:24 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
  2026-08-20 11:17 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-08-26 21:33 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
  2026-08-27 06:56 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
  2026-09-30 12:31 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
  [15+ messages in thread]

BUG #19734: NOT IN type resolution differs for outer Vars, producing different query results
  2026-09-30 12:03 UTC  PG Bug reporting form <noreply@postgresql.org>

REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-06-24 21:57 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-06-26 00:12 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-07-06 11:03 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-07-08 22:54 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-07-09 14:48 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-08-10 11:41 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-09-30 04:32 UTC  Paul Kim <mok03127@gmail.com>
  [7+ messages in thread]

BUG #19729: Error de memoria compartida
  2026-09-29 16:06 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort
  2026-09-11 20:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort
  2026-09-12 16:45 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort
  2026-09-12 19:06 UTC  Samriddha Kumar Tripathi <sumitkumartripathi0@gmail.com>
` Re: BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort
  2026-09-13 06:36 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort
  2026-09-14 09:34 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort
  2026-09-28 15:41 UTC  Trakshan Mishra <trakshanmishra477@gmail.com>
  [6+ messages in thread]

BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
  2026-09-26 09:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
  2026-09-26 14:25 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
  2026-09-28 04:44 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
  2026-09-28 14:00 UTC  Rafia Sabih <rafia.pghackers@gmail.com>
  [4+ messages in thread]

BUG #19724: ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
  2026-09-26 13:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19724: ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
  2026-09-28 13:31 UTC  Nitin Motiani <nitinmotiani@google.com>
  [2+ messages in thread]

BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-13 16:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-15 08:59 UTC  Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-27 16:11 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-27 16:14 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-27 19:05 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-27 20:35 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
  2026-09-28 04:13 UTC  Peter Geoghegan <pg@bowt.ie>
  [7+ messages in thread]

BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-15 03:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-16 14:29 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-18 02:06 UTC  =?ISO-8859-1?B?emVuZ21hbg==?= <zengman@halodbtech.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-18 08:56 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-04 10:38 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-23 20:12 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-24 17:06 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-24 17:38 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-26 16:28 UTC  jian he <jian.universality@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-26 18:14 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-28 04:03 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [11+ 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>
  [3+ messages in thread]

BUG #19688: pg_dump --schema scans all sequences in PostgreSQL 18, causing severe performance regression
  2026-09-14 20:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19688: pg_dump --schema scans all sequences in PostgreSQL 18, causing severe performance regression
  2026-09-26 19:01 UTC  Andrew Krylosov <krylosov.andrew@gmail.com>
  [2+ messages in thread]

BUG #19718: pg_dump -Ft: restore.sql gets "\unrestrict (null)"/"\restrict (null)", so psql skips \i data files
  2026-09-24 21:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19718: pg_dump -Ft: restore.sql gets "\unrestrict (null)"/"\restrict (null)", so psql skips \i data files
  2026-09-26 16:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19722: Window PARTITION BY numeric treats equal values with different scales as separate partitions
  2026-09-26 08:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19722: Window PARTITION BY numeric treats equal values with different scales as separate partitions
  2026-09-26 14:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
  2026-07-21 06:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
  2026-07-27 17:47 UTC  Pritt Balagopal <pritt1999@gmail.com>
` Re: BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
  2026-09-20 11:12 UTC  Pritt Balagopal <pritt1999@gmail.com>
` Re: BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
  2026-09-26 10:10 UTC  Pritt Balagopal <pritt1999@gmail.com>
  [4+ messages in thread]

BUG #19721: json_value with DEFAULT ON ERROR returns inconsistent results for NULL input in materialized CTE
  2026-09-26 06:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19721: json_value with DEFAULT ON ERROR returns inconsistent results for NULL input in materialized CTE
  2026-09-26 08:55 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [2+ messages in thread]

BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-22 16:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-23 19:02 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 04:22 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 05:56 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 06:13 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 06:16 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 06:34 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 06:44 UTC  jian he <jian.universality@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 22:52 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-24 23:46 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-25 01:04 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-25 19:35 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-25 19:45 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
  2026-09-25 23:53 UTC  Michael Paquier <michael@paquier.xyz>
  [14+ messages in thread]

BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
  2026-09-18 07:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
  2026-09-25 04:59 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
  2026-09-25 05:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
  2026-09-25 13:35 UTC  shihao zhong <zhong950419@gmail.com>
  [4+ messages in thread]

BUG #19719: BUG: huge_pages=on shared memory reattached without FILE_MAP_LARGE_PAGES on Windows
  2026-09-25 04:39 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
  2026-09-22 16:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
  2026-09-25 04:37 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

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>
  [6+ messages in thread]

BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-14 05:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-14 19:07 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-15 06:57 UTC  Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-23 18:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-23 18:59 UTC  Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-23 19:39 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-24 01:19 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
  2026-09-24 02:47 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
  [8+ messages in thread]

BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-20 11:57 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-20 20:05 UTC  Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-20 20:52 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-20 21:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-21 23:31 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-22 04:34 UTC  Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
  2026-09-24 01:02 UTC  shihao zhong <zhong950419@gmail.com>
  [7+ messages in thread]

BUG #19641: Unexpected results on an SP-GiST indexed column with a non-deterministic collation
  2026-08-28 04:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19641: Unexpected results on an SP-GiST indexed column with a non-deterministic collation
  2026-08-28 19:38 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19641: Unexpected results on an SP-GiST indexed column with a non-deterministic collation
  2026-09-23 19:50 UTC  Manu <manuelreyesbravo@gmail.com>
  [3+ messages in thread]

BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-08-03 06:58 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-09-23 19:40 UTC  Manu <manuelreyesbravo@gmail.com>
  [2+ messages in thread]

TID Range Scans can return wrong results after scanning backwards
  2026-09-16 20:07 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: TID Range Scans can return wrong results after scanning backwards
  2026-09-17 07:13 UTC  Ewan Young <kdbase.hack@gmail.com>
` Re: TID Range Scans can return wrong results after scanning backwards
  2026-09-23 13:34 UTC  David Rowley <dgrowleyml@gmail.com>
  [3+ 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