pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Lost FOR KEY SHARE lock
  2026-11-02 14:07 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Lost FOR KEY SHARE lock
  2026-11-17 02:10 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

BUG #18754: Logical replication cannot restart if client sent a copyDone
  2024-12-27 12:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18754: Logical replication cannot restart if client sent a copyDone
  2025-01-01 10:14 UTC  vignesh C <vignesh21@gmail.com>
` Re: BUG #18754: Logical replication cannot restart if client sent a copyDone
  2026-11-12 12:55 UTC  Kacper Kuras <kacperkuras@hotmail.com>
` RE: BUG #18754: Logical replication cannot restart if client sent a copyDone
  2026-11-17 01:42 UTC  Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
  [4+ messages in thread]

BUG #19903: ALTER COLUMN TYPE: "unexpected object depending on column" internal error via partition key
  2026-11-15 04:47 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19903: ALTER COLUMN TYPE: "unexpected object depending on column" internal error via partition key
  2026-11-16 20:11 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #19903: ALTER COLUMN TYPE: "unexpected object depending on column" internal error via partition key
  2026-11-16 22:53 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #19903: ALTER COLUMN TYPE: "unexpected object depending on column" internal error via partition key
  2026-11-16 23:01 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #19903: ALTER COLUMN TYPE: "unexpected object depending on column" internal error via partition key
  2026-11-16 23:57 UTC  Andres Freund <andres@anarazel.de>
  [5+ messages in thread]

BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
  2026-11-16 14:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
  2026-11-16 20:16 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
  2026-11-16 20:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
  2026-11-16 21:36 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
  2026-11-16 21:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

ALTER TABLE DROP/ADD COLUMN leaves rows in wrong partition on whole-row key
  2026-11-16 20:28 UTC  Michael Malis <malis@pgrust.com>

GiST: SERIALIZABLE misses conflict when scan prunes at internal page
  2026-11-16 20:28 UTC  Michael Malis <malis@pgrust.com>

dbase_redo: XLOG_DBASE_CREATE_FILE_COPY replay empties live database
  2026-11-16 20:28 UTC  Michael Malis <malis@pgrust.com>

Hot Standby: missing snapshot conflicts in CREATE INDEX, rewrite, hash
  2026-11-16 20:28 UTC  Michael Malis <malis@pgrust.com>

BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
  2026-11-15 04:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
  2026-11-16 12:23 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
  2026-11-16 18:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
  2026-11-16 18:49 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
  2026-11-16 19:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
  2026-11-16 19:33 UTC  Daniel Gustafsson <daniel@yesql.se>
  [6+ messages in thread]

Two bugs around ALTER TYPE
  2026-04-14 11:53 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Two bugs around ALTER TYPE
  2026-06-24 23:56 UTC  surya poondla <suryapoondla4@gmail.com>
` Re: Two bugs around ALTER TYPE
  2026-07-20 21:24 UTC  surya poondla <suryapoondla4@gmail.com>
` Re: Two bugs around ALTER TYPE
  2026-07-21 09:55 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Two bugs around ALTER TYPE
  2026-11-10 11:32 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Two bugs around ALTER TYPE
  2026-11-16 07:47 UTC  Rui Zhao <zhaorui126@gmail.com>
` Re: Two bugs around ALTER TYPE
  2026-11-16 19:14 UTC  Andres Freund <andres@anarazel.de>
  [7+ messages in thread]

PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-09-27 06:07 UTC  Jacky Nguyen <nktpro@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-09-27 10:33 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-09-28 06:37 UTC  shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-01 15:07 UTC  rahul@rhyadav.dev
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-02 05:15 UTC  shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-02 07:00 UTC  rahul@rhyadav.dev
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-03 04:12 UTC  shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-08 15:02 UTC  Rahul <rahul@rhyadav.dev>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-09 03:13 UTC  shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-13 20:12 UTC  Melanie Plageman <melanieplageman@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-10-14 03:20 UTC  shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-11-16 16:03 UTC  Melanie Plageman <melanieplageman@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-11-16 17:10 UTC  shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-11-16 18:13 UTC  Melanie Plageman <melanieplageman@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
  2026-11-16 19:07 UTC  shihao zhong <zhong950419@gmail.com>
  [15+ messages in thread]

BUG #19772: ERROR: corrupt MVNDistinct entry for GROUP BY c0, ROLLUP (abs(c0)) with ndistinct statistics
  2026-10-18 23:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19772: ERROR: corrupt MVNDistinct entry for GROUP BY c0, ROLLUP (abs(c0)) with ndistinct statistics
  2026-10-20 19:30 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19772: ERROR: corrupt MVNDistinct entry for GROUP BY c0, ROLLUP (abs(c0)) with ndistinct statistics
  2026-11-16 10:45 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19772: ERROR: corrupt MVNDistinct entry for GROUP BY c0, ROLLUP (abs(c0)) with ndistinct statistics
  2026-11-16 16:07 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
  [4+ messages in thread]

BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-10-30 06:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-01 06:23 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-02 02:40 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-02 12:46 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-04 03:34 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-05 09:28 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-08 01:15 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
  2026-11-16 14:02 UTC  Joao Rito <joaovictor.rito@gmail.com>
  [8+ messages in thread]

BUG #19907: INSERT through partitioned table fails with domain-typed generated column
  2026-11-16 12:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19907: INSERT through partitioned table fails with domain-typed generated column
  2026-11-16 12:38 UTC  Bjorn Pagen <hello@bjornpagen.com>
  [2+ messages in thread]

BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-11 05:33 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-12 04:00 UTC  Ajin Cherian <itsajin@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-12 05:20 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-12 10:12 UTC  Ajin Cherian <itsajin@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-12 10:37 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-12 12:16 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-13 03:51 UTC  Ajin Cherian <itsajin@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-13 06:28 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-13 08:42 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-13 09:31 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-13 10:10 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-14 10:48 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-16 03:54 UTC  shveta malik <shveta.malik@gmail.com>
` Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION
  2026-11-16 04:55 UTC  shveta malik <shveta.malik@gmail.com>
  [14+ messages in thread]

BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-02 22:35 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-11 10:26 UTC  민영재 <dudwo990413@gmail.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-12 03:42 UTC  QQ Mail <781408517@qq.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-12 06:35 UTC  QQ Mail <781408517@qq.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-12 07:15 UTC  민영재 <dudwo990413@gmail.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-16 20:41 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-10-17 14:53 UTC  민영재 <dudwo990413@gmail.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-11-09 07:45 UTC  민영재 <dudwo990413@gmail.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-11-15 08:46 UTC  Joao Rito <joaovictor.rito@gmail.com>
` Re: BUG #19736: `JSON_OBJECT ... ABSENT ON NULL` accepts invalid keys when the value is NULL
  2026-11-15 16:22 UTC  민영재 <dudwo990413@gmail.com>
  [10+ messages in thread]

BUG #19898: int4_avg_accum_inv wraps below INT64_MIN instead of raising an error
  2026-11-12 23:42 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19898: int4_avg_accum_inv wraps below INT64_MIN instead of raising an error
  2026-11-15 06:54 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-08-03 05:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-08-03 15:26 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-10-28 09:08 UTC  Ishjaap Singh <ishjaap.singh07@gmail.com>
` Re: BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-11-13 18:43 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-11-15 06:39 UTC  Ishjaap Singh <ishjaap.singh07@gmail.com>
  [5+ messages in thread]

BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-10-29 22:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-09 05:21 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-09 18:31 UTC  Marcos Castedo <marcos.castedo@anachronics.com>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-09 19:21 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-09 20:04 UTC  Marcos Castedo <marcos.castedo@anachronics.com>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-09 22:59 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-11 16:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-11 17:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-12 04:52 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-12 16:48 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
  2026-11-15 05:02 UTC  shihao zhong <zhong950419@gmail.com>
  [11+ messages in thread]

BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-09-19 13:44 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-09-20 15:49 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-09-20 18:33 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-09-20 19:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-09-20 19:29 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-11-15 03:53 UTC  Joao Rito <joaovictor.rito@gmail.com>
` Re: BUG #19703: information_schema.usage_privileges omits a sequence owner's implicit USAGE privilege
  2026-11-15 03:59 UTC  shihao zhong <zhong950419@gmail.com>
  [7+ messages in thread]

BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-08-17 14:04 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-08-17 14:09 UTC  zengman <zengman@halodbtech.com>
` Re:BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-08-24 03:37 UTC  zengman <zengman@halodbtech.com>
` Re: BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-10-12 03:33 UTC  QQ Mail <781408517@qq.com>
` Re: BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-11-12 01:23 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-11-12 14:50 UTC  zengman <zengman@halodbtech.com>
` Re: BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
  2026-11-15 03:54 UTC  Joao Rito <joaovictor.rito@gmail.com>
  [7+ messages in thread]

BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-09-19 11:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-09-19 14:59 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-11-09 22:26 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-11-09 22:43 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-11-10 09:23 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-11-13 00:00 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-11-13 17:49 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19702: decode() accepts Base64 payload after terminal padding
  2026-11-15 03:51 UTC  shihao zhong <zhong950419@gmail.com>
  [8+ messages in thread]

BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point
  2023-12-24 15:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point
  2026-11-10 03:29 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point
  2026-11-13 06:58 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point
  2026-11-15 03:41 UTC  shihao zhong <zhong950419@gmail.com>
  [4+ messages in thread]

bug: Gather rescan keeps the first scan's tuple bound in workers
  2026-09-18 22:57 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: bug: Gather rescan keeps the first scan's tuple bound in workers
  2026-09-19 03:05 UTC  shihao zhong <zhong950419@gmail.com>
` Re: bug: Gather rescan keeps the first scan's tuple bound in workers
  2026-11-12 09:46 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: bug: Gather rescan keeps the first scan's tuple bound in workers
  2026-11-12 15:45 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: bug: Gather rescan keeps the first scan's tuple bound in workers
  2026-11-15 03:33 UTC  shihao zhong <zhong950419@gmail.com>
  [5+ messages in thread]

BUG #19902: DECLARE CURSOR over trigger transition table fails with XX000
  2026-11-15 03:32 UTC  PG Bug reporting form <noreply@postgresql.org>


[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