agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19643: Output of jsonb_populate_recordset not consistent with documentation description
2026-08-28 12:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19643: Output of jsonb_populate_recordset not consistent with documentation description
2026-08-28 13:28 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #19642: Include column name in error message when varchar(n) length limit is exceeded
2026-08-28 04:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19642: Include column name in error message when varchar(n) length limit is exceeded
2026-08-28 13:16 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #19498: Anonymous ROW() field expansion fails after scalar subquery relay
2026-05-27 11:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19498: Anonymous ROW() field expansion fails after scalar subquery relay
2026-08-27 21:20 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
MERGE/SPLIT PARTITIONS issues/questions
2026-07-23 11:59 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-07-23 14:29 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-01 09:49 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-01 11:11 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-02 04:27 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-02 06:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-03 19:26 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-05 01:27 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-05 17:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-06 03:45 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-06 22:59 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-11 21:36 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-12 20:38 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-12 20:48 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-12 20:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 14:07 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 14:36 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 14:51 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 15:49 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-17 10:27 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-17 10:31 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-17 10:35 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-18 03:47 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-19 11:31 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-19 11:58 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-20 07:41 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-20 11:46 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-21 09:36 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-21 13:48 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-21 14:17 UTC Alexander Korotkov <aekorotkov@gmail.com>
` RE: MERGE/SPLIT PARTITIONS issues/questions
2026-08-23 06:37 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: MERGE/SPLIT PARTITIONS issues/questions
2026-08-23 09:17 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-24 10:39 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-24 22:16 UTC Robert Haas <robertmhaas@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 09:05 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 16:37 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 16:42 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 23:39 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-27 20:24 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-27 20:40 UTC Robert Haas <robertmhaas@gmail.com>
[40+ messages in thread]
BUG #19640: Standby permanently stuck re-requesting old timeline after promotion, never switches to new timeline
2026-08-26 11:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19640: Standby permanently stuck re-requesting old timeline after promotion, never switches to new timeline
2026-08-27 16:17 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[2+ messages in thread]
BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-02 22:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-08 04:15 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-08 06:52 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-12 21:16 UTC Si, Evan <evsi@amazon.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-13 16:59 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-13 19:06 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-13 19:11 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 18:15 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 18:18 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 20:26 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 21:07 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-15 07:32 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-15 20:27 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-23 18:22 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-26 14:38 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-26 22:02 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-26 23:28 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-27 15:49 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[18+ messages in thread]
BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-19 03:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-19 15:22 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-19 16:12 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-20 09:06 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-20 22:30 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-21 05:18 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-21 08:41 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-24 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-24 23:49 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-25 05:14 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-27 14:45 UTC Fujii Masao <masao.fujii@gmail.com>
[11+ messages in thread]
BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-23 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-24 13:30 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-25 19:28 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-25 20:01 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-26 00:50 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-26 03:08 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-27 09:59 UTC Peter Eisentraut <peter@eisentraut.org>
[7+ messages in thread]
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>
[14+ messages in thread]
SIGSEGV in dynahash
2026-08-15 13:06 UTC Konstantin Knizhnik <knizhnik@garret.ru>
` Re: SIGSEGV in dynahash
2026-08-15 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SIGSEGV in dynahash
2026-08-15 23:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: SIGSEGV in dynahash
2026-08-20 13:19 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: SIGSEGV in dynahash
2026-08-25 04:30 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: SIGSEGV in dynahash
2026-08-25 11:14 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[6+ messages in thread]
BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-23 23:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 14:05 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 16:33 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 16:51 UTC Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 18:19 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 18:52 UTC Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 19:34 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
2026-08-24 19:42 UTC Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
[8+ messages in thread]
BUG #19639: EXPLAIN (FORMAT JSON) emits a 309-digit cost value, and the node still reports "Disabled": false
2026-08-23 23:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19639: EXPLAIN (FORMAT JSON) emits a 309-digit cost value, and the node still reports "Disabled": false
2026-08-24 13:52 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19639: EXPLAIN (FORMAT JSON) emits a 309-digit cost value, and the node still reports "Disabled": false
2026-08-24 17:01 UTC Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
[3+ 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 =?gb18030?B?emVuZ21hbg==?= <zengman@halodbtech.com>
` Re:BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false'
2026-08-24 03:37 UTC =?gb18030?B?emVuZ21hbg==?= <zengman@halodbtech.com>
[3+ 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>
[27+ messages in thread]
on 19beta3: repack (concurrently) affects sessions with transaction isolation level repeatable read
2026-08-22 07:29 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: on 19beta3: repack (concurrently) affects sessions with transaction isolation level repeatable read
2026-08-22 19:45 UTC Peter Geoghegan <pg@bowt.ie>
` Re: on 19beta3: repack (concurrently) affects sessions with transaction isolation level repeatable read
2026-08-23 09:31 UTC Jochen Bandhauer <jb@jbitc.de>
[3+ messages in thread]
BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash
2026-07-01 08:12 UTC Alessandro Regolini <alessandro@regolini.it>
` Re: BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash
2026-07-02 18:32 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash
2026-08-10 07:44 UTC Alessandro Regolini <alessandro@regolini.it>
` Re: BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash
2026-08-22 20:29 UTC Peter Geoghegan <pg@bowt.ie>
[4+ messages in thread]
BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-01 03:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-01 15:16 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-04 08:05 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-04 10:40 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-04 11:42 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-04 16:38 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-04 17:10 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-05 02:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-05 04:41 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19593: area(circle) silently returns Infinity instead of raising "value out of range: overflow"
2026-08-22 05:28 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[10+ messages in thread]
BUG #19636: heap_fill_tuple misses short varlena conversion after EOH_flatten_into, causing 3-byte waste per row
2026-08-21 09:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19636: heap_fill_tuple misses short varlena conversion after EOH_flatten_into, causing 3-byte waste per row
2026-08-21 14:37 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19636: heap_fill_tuple misses short varlena conversion after EOH_flatten_into, causing 3-byte waste per row
2026-08-21 22:07 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[3+ messages in thread]
BUG #19634: Hash partition with large MODULUS causes "invalid memory alloc request size"
2026-08-21 03:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19634: Hash partition with large MODULUS causes "invalid memory alloc request size"
2026-08-21 12:04 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19634: Hash partition with large MODULUS causes "invalid memory alloc request size"
2026-08-21 12:24 UTC Andres Freund <andres@anarazel.de>
[3+ messages in thread]
BUG #19630: FOR PORTION OF crashes with XX000 when target range is NULL
2026-08-19 03:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19630: FOR PORTION OF crashes with XX000 when target range is NULL
2026-08-19 11:11 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19630: FOR PORTION OF crashes with XX000 when target range is NULL
2026-08-21 12:16 UTC Peter Eisentraut <peter@eisentraut.org>
[3+ messages in thread]
BUG #19635: Missing entry in information_schema.sequences when creating a Tale with auto increment
2026-08-21 09:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19635: Missing entry in information_schema.sequences when creating a Tale with auto increment
2026-08-21 12:00 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 03:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 10:10 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 10:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 23:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 08:29 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 08:58 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 22:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 22:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-21 11:34 UTC Álvaro Herrera <alvherre@kurilemu.de>
[9+ messages in thread]
BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-02 17:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-04 08:54 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-05 06:03 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-07 01:58 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-10 05:47 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-10 08:23 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-11 00:40 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-12 08:09 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-14 06:33 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-14 14:08 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-17 03:23 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-19 17:57 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-21 07:55 UTC Fujii Masao <masao.fujii@gmail.com>
[13+ messages in thread]
pg_restore: stack-buffer-overflow(read) in _tarGetHeader() in pg_backup_tar.c
2026-08-20 13:22 UTC Ilia Kashintsev <ilia.kashintsev@gmail.com>
BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-17 04:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 01:28 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 01:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 02:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 07:06 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox