pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19798: "failed to build any 4-way joins" with ROLLUP over a LATERAL subquery that references the nullable s
  2026-10-26 13:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19798: "failed to build any 4-way joins" with ROLLUP over a LATERAL subquery that references the nullable s
  2026-10-27 06:35 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19798: failed to build any 4-way joins
  2026-11-15 03:08 UTC  Joao Rito <joaovictor.rito@gmail.com>
  [3+ messages in thread]

BUG #19807: CHECK constraint not enforced on partitioned table when partition overrides a virtual generated colu
  2026-10-29 06:17 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19807: CHECK constraint not enforced on partitioned table when partition overrides a virtual generated colu
  2026-11-09 10:49 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19807: CHECK constraint not enforced on partitioned table
  2026-11-14 21:33 UTC  Joao Rito <joaovictor.rito@gmail.com>
  [3+ messages in thread]

BUG #19837: ORDER BY/DISTINCT ON use wrong column with grouping set duplicates
  2026-11-06 19:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19837: ORDER BY/DISTINCT ON use wrong column with grouping set duplicates
  2026-11-13 21:17 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19837: ORDER BY/DISTINCT ON use wrong column with grouping set duplicates
  2026-11-14 10:50 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [3+ messages in thread]

BUG #19884: pg_publication_tables omits a detach-pending partition in root mode
  2026-11-11 14:13 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19884: pg_publication_tables omits a detach-pending partition in root mode
  2026-11-12 21:45 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19884: pg_publication_tables omits a detach-pending partition in root mode
  2026-11-13 04:42 UTC  Nisha Moond <nisha.moond412@gmail.com>
` Re: BUG #19884: pg_publication_tables omits a detach-pending partition in root mode
  2026-11-14 01:44 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
  [4+ 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>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-10 13:42 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-11 01:22 UTC  JaeHyuck Sa <jaehyuck.sa.dev@gmail.com>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-11 05:09 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-12 05:29 UTC  JaeHyuck Sa <jaehyuck.sa.dev@gmail.com>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-12 23:00 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-13 06:10 UTC  JaeHyuck Sa <jaehyuck.sa.dev@gmail.com>
` Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
  2026-11-13 19:54 UTC  Manu <manuelreyesbravo@gmail.com>
  [9+ messages in thread]

BUG #19866: acldefault() emits invalid UTF-8 for a high-bit "char" value
  2026-11-11 05:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19866: acldefault() emits invalid UTF-8 for a high-bit "char" value
  2026-11-13 19:10 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [2+ messages in thread]

BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-07 04:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-09 05:28 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-10 03:49 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-10 03:52 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-11 01:54 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-11 06:34 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-12 01:34 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-12 21:07 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-13 06:02 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
  2026-11-13 16:07 UTC  Corey Huinker <corey.huinker@gmail.com>
  [10+ messages in thread]

BUG #19900: No yum repo for RHEL 10.3 yet
  2026-11-13 13:55 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19886: pg_terminate_backend timeout expires early after latch wakeups
  2026-11-11 14:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #19886: pg_terminate_backend timeout expires early after latch wakeups
  2026-11-13 12:51 UTC  Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
  [2+ messages in thread]

BUG #19896: transaction_timeout misbehaves after ROLLBACK TO SAVEPOINT and after errors
  2026-11-12 12:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19896: transaction_timeout misbehaves after ROLLBACK TO SAVEPOINT and after errors
  2026-11-13 09:33 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
  [2+ messages in thread]

to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-22 14:18 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-23 07:57 UTC  Michael Paquier <michael@paquier.xyz>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-23 08:11 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-23 08:26 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-23 15:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-23 16:36 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-23 22:14 UTC  Michael Paquier <michael@paquier.xyz>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-24 08:12 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-24 08:16 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-24 09:13 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-24 12:44 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-24 12:50 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-24 15:41 UTC  Peter Eisentraut <peter@eisentraut.org>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-26 22:43 UTC  Michael Paquier <michael@paquier.xyz>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-27 07:23 UTC  Michael Paquier <michael@paquier.xyz>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-27 10:54 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-30 14:14 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-04-30 22:57 UTC  Michael Paquier <michael@paquier.xyz>
` Re: to_date()/to_timestamp() silently accept month=0 and day=0
  2026-11-13 08:16 UTC  Maxim Orlov <orlovmg@gmail.com>
  [19+ messages in thread]

VACUUM/ANALYZE double-count the backend's own pending table stats (n_live_tup = 2*N after INSERT + ANALYZE)
  2026-10-14 10:39 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-14 18:47 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-14 20:28 UTC  Sebastian Webber <sebastian@swebber.me>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-14 22:53 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-15 06:08 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-15 07:11 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-15 07:48 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-15 07:52 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-10-15 08:05 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-11-05 05:48 UTC  Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-11-05 07:07 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-11-12 02:41 UTC  João Rito <joaovictor.rito@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-11-12 04:43 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-11-12 11:23 UTC  João Rito <joaovictor.rito@gmail.com>
` Re: VACUUM/ANALYZE double-count the backend's own pending table stats
  2026-11-13 07:34 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
  [15+ messages in thread]

BUG #19800: Wrong results: self-join elimination drops an ORDER BY sort key with GROUPING SETS / CUBE / ROLLUP
  2026-10-27 07:36 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19800: Wrong results: self-join elimination drops an ORDER BY sort key with GROUPING SETS / CUBE / ROLLUP
  2026-10-27 09:28 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19800: Wrong results: self-join elimination drops an ORDER BY sort key with GROUPING SETS / CUBE / ROLLUP
  2026-10-29 06:41 UTC  Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19800: Wrong results: self-join elimination drops an ORDER BY sort key with GROUPING SETS / CUBE / ROLLUP
  2026-11-11 06:38 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19800: Wrong results: self-join elimination drops an ORDER BY sort key with GROUPING SETS / CUBE / ROLLUP
  2026-11-12 21:34 UTC  Narayanan Venkateswaran <narayananvpostgres@gmail.com>
  [5+ messages in thread]

BUG #19883: Partition pruning errors on SubPlan inside = ANY array
  2026-11-11 14:04 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19883: Partition pruning errors on SubPlan inside = ANY array
  2026-11-12 20:19 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [2+ messages in thread]

BUG #19848: BEGIN ATOMIC with unnamed/OUT params breaks restore and pg_upgrade
  2026-11-07 15:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19848: BEGIN ATOMIC with unnamed/OUT params breaks restore and pg_upgrade
  2026-11-07 15:16 UTC  Atisss hh <125atishprak@gmail.com>
` Re: BUG #19848: BEGIN ATOMIC with unnamed/OUT params breaks restore and pg_upgrade
  2026-11-12 03:13 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19848: BEGIN ATOMIC with unnamed/OUT params breaks restore and pg_upgrade
  2026-11-12 16:22 UTC  Atisss hh <125atishprak@gmail.com>
` Re: BUG #19848: BEGIN ATOMIC with unnamed/OUT params breaks restore and pg_upgrade
  2026-11-12 19:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

BUG #19894: CREATE DATABASE logs all-zeros visibility map
  2026-11-12 00:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19894: CREATE DATABASE logs all-zeros visibility map
  2026-11-12 06:51 UTC  Сергей Шиндерук <s.shinderuk@postgrespro.ru>
` Re: BUG #19894: CREATE DATABASE logs all-zeros visibility map
  2026-11-12 17:40 UTC  Christophe Pettus <xof@thebuild.com>
` Re: BUG #19894: CREATE DATABASE logs all-zeros visibility map
  2026-11-12 18:18 UTC  Сергей Шиндерук <s.shinderuk@postgrespro.ru>
  [4+ messages in thread]

BUG #19887: cube expression index returns wrong rows after extra_float_digits change
  2026-11-11 15:07 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19887: cube expression index returns wrong rows after extra_float_digits change
  2026-11-12 18:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19885: pg_input_is_valid(tsquery) throws stack depth error instead of returning false
  2026-11-11 14:37 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19885: pg_input_is_valid(tsquery) throws stack depth error instead of returning false
  2026-11-12 17:33 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-02 15:36 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-02 15:39 UTC  Venu K <venu2805k@gmail.com>
` Re: BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-03 03:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-03 05:23 UTC  Venu K <venu2805k@gmail.com>
` Re: BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-11 20:23 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-12 16:13 UTC  Venu K <venu2805k@gmail.com>
` Re: BUG #19826: corr()/regr_r2() of constant input: NULL serially, 1 with partial aggregation
  2026-11-12 17:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [7+ messages in thread]

BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-07 01:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-07 01:26 UTC  Atisss hh <125atishprak@gmail.com>
` Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-08 15:11 UTC  Zhijie Hou <houzhijie22@gmail.com>
` Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-09 10:53 UTC  Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-09 11:46 UTC  Zhijie Hou <houzhijie22@gmail.com>
` Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-09 14:47 UTC  Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
  2026-11-12 15:40 UTC  Atisss hh <125atishprak@gmail.com>
  [7+ messages in thread]

BUG #19834: eager aggregation still evaluates volatile join clauses when the volatile function is inside a SubPl
  2026-11-05 09:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19834: eager aggregation still evaluates volatile join clauses when the volatile function is inside a SubPl
  2026-11-09 05:16 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19834: eager aggregation still evaluates volatile join clauses when the volatile function is inside a SubPl
  2026-11-11 21:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19834: eager aggregation still evaluates volatile join clauses when the volatile function is inside a SubPl
  2026-11-12 05:05 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19834: eager aggregation still evaluates volatile join clauses when the volatile function is inside a SubPl
  2026-11-12 15:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-06-14 07:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-06-17 17:03 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-03 06:45 UTC  Imran Zaheer <imran.zhir@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-06 06:36 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-06 13:38 UTC  Konstantin Knizhnik <knizhnik@garret.ru>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-06 18:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-06 18:21 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-06 23:18 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-06 23:51 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-07 01:42 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-07 05:21 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-07 17:10 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-07 22:15 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-08 01:10 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-08 12:00 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-08 15:00 UTC  Imran Zaheer <imran.zhir@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-08 22:49 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-09 02:47 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-09 05:17 UTC  Konstantin Knizhnik <knizhnik@garret.ru>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-09 05:43 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-09 10:08 UTC  Konstantin Knizhnik <knizhnik@garret.ru>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-17 10:22 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-21 15:44 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` RE: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-24 11:39 UTC  Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-07-30 19:54 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-08-05 18:18 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-08-23 17:12 UTC  Rui Zhao <zhaorui126@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-10-09 12:56 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-10-12 10:57 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-10-24 04:41 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-10-24 15:36 UTC  Rui Zhao <zhaorui126@gmail.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-11-12 12:47 UTC  Konstantin Knizhnik <konstantin.knizhnik@databricks.com>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
  2026-11-12 12:49 UTC  Konstantin Knizhnik <knizhnik@garret.ru>
  [33+ messages in thread]

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>
` Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
  2026-11-10 05:18 UTC  Sho Ito <i.sho.0628@gmail.com>
` Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
  2026-11-10 23:30 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
  2026-11-11 01:03 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
  2026-11-12 12:44 UTC  Daniel Gustafsson <daniel@yesql.se>
  [6+ messages in thread]

Lost walsender wakeup stalls synchronous commits until the standby's next reply (16+)
  2026-11-01 01:26 UTC  Alex Speller <alex@alexspeller.com>
` Re: Lost walsender wakeup stalls synchronous commits until the standby's next reply (16+)
  2026-11-02 16:05 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: Lost walsender wakeup stalls synchronous commits until the standby's next reply (16+)
  2026-11-02 21:23 UTC  alex@alexspeller.com
` Re: Lost walsender wakeup stalls synchronous commits until the standby's next reply (16+)
  2026-11-03 01:56 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: Lost walsender wakeup stalls synchronous commits until the standby's next reply (16+)
  2026-11-12 01:42 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: Lost walsender wakeup stalls synchronous commits until the standby's next reply (16+)
  2026-11-12 11:35 UTC  Xuneng Zhou <xunengzhou@gmail.com>
  [6+ messages in thread]

BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-09 13:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-10 17:01 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-10 21:36 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-11 01:50 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-11 07:41 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-11 13:46 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-11 22:40 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-12 01:26 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-12 01:32 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-12 04:47 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-12 04:55 UTC  Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-12 05:10 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats
  2026-11-12 05:31 UTC  Corey Huinker <corey.huinker@gmail.com>
  [13+ 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