pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 11:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 11:45 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 11:48 UTC Matthias Hörmann <matthias.hoermann@saltation.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 19:09 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 19:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 19:34 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 20:58 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-10 05:26 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-10 09:24 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-22 21:23 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-22 21:53 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-24 22:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-27 14:30 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-27 19:49 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-27 21:21 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-29 15:24 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-29 15:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-29 20:19 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-11-03 20:57 UTC Peter Eisentraut <peter@eisentraut.org>
[20+ messages in thread]
BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-02 15:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-02 16:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-02 16:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re:Re: BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-03 02:48 UTC dqetool <dqetool@126.com>
[4+ messages in thread]
Inconsistencies around Composite Row nullness
2025-11-02 16:52 UTC Chris Hanks <christopher.m.hanks@gmail.com>
` Re: Inconsistencies around Composite Row nullness
2025-11-02 18:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistencies around Composite Row nullness
2025-11-02 18:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
=?gb18030?B?u9i4tKO6IFtidWcgcmVwb3J0XSBBYm91dCBjcmVh?= =?gb18030?B?dGUgdGFibGUgbGlrZSBmZWF0dXJlJ3MgYnVn?=
2025-10-31 09:45 UTC =?gb18030?B?ZGVuZ2thaQ==?= <784523565@qq.com>
[bug report] About create table like feature's bug
2025-10-31 07:14 UTC =?gb18030?B?ZGVuZ2thaQ==?= <784523565@qq.com>
` Re: [bug report] About create table like feature's bug
2025-10-31 08:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages
2025-10-28 09:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages
2025-10-29 19:08 UTC Tomas Vondra <tomas@vondra.me>
[2+ messages in thread]
BUG #19097: System catalog modifications are allowed by alter
2025-10-29 04:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 11:31 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 11:32 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 12:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 14:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-12 16:39 UTC Tushar Takate <tushar11.takate@gmail.com>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-12 21:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-13 01:10 UTC Tushar Takate <tushar11.takate@gmail.com>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-13 01:24 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-13 04:38 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-10-28 21:34 UTC surya poondla <suryapoondla4@gmail.com>
[6+ messages in thread]
Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-16 09:46 UTC Dmitry Fomin <fomin.list@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-17 01:21 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-17 09:08 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-17 10:36 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-20 13:48 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-20 19:27 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 01:28 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 05:20 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 09:11 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 11:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 13:49 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 20:29 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-23 12:07 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-25 22:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-28 12:44 UTC Amit Langote <amitlangote09@gmail.com>
[15+ messages in thread]
psql --echo-queries does not echo all queries
2025-10-24 18:16 UTC Gavin Wahl <gavinwahl@gmail.com>
` Re: psql --echo-queries does not echo all queries
2025-10-25 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql --echo-queries does not echo all queries
2025-10-27 22:24 UTC Gavin Wahl <gavinwahl@gmail.com>
[3+ messages in thread]
BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-21 07:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-21 13:14 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-21 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-23 00:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-23 15:05 UTC Jacob Champion <jacob.champion@enterprisedb.com>
[5+ messages in thread]
Automating Failover Resync & Re-Attach in pgpool2
2025-10-10 12:17 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: Automating Failover Resync & Re-Attach in pgpool2
2025-10-17 07:55 UTC Bo Peng <pengbo@sraoss.co.jp>
` Re: Automating Failover Resync & Re-Attach in pgpool2
2025-10-17 08:00 UTC Bo Peng <pengbo@sraoss.co.jp>
` Fwd: Automating Failover Resync & Re-Attach in pgpool2
2025-10-23 07:13 UTC VASUKI M <vasukim1992002@gmail.com>
[4+ messages in thread]
ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 07:33 UTC Emmanuel Touzery <emmanuel.touzery@plandela.si>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 08:02 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 08:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 08:48 UTC Emmanuel Touzery <emmanuel.touzery@plandela.si>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 11:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 11:27 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 21:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-22 21:13 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-23 00:20 UTC David Rowley <dgrowleyml@gmail.com>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-23 06:30 UTC Emmanuel Touzery <emmanuel.touzery@plandela.si>
` Re: ERROR: XX000: could not find memoization table entry (reproducible)
2025-10-23 06:41 UTC David Rowley <dgrowleyml@gmail.com>
[11+ messages in thread]
BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
2025-10-22 12:16 UTC Ishan Arunkumar Joshi <ishan.joshi@netcracker.com>
` Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
2025-10-22 21:36 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
2025-10-22 22:41 UTC Euler Taveira <euler@eulerto.com>
` RE: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
2025-10-23 04:48 UTC Ishan Arunkumar Joshi <ishan.joshi@netcracker.com>
[4+ messages in thread]
Version 18.0 of postgres image in dockerhub - container crashes when starting up
2025-10-21 12:21 UTC Yuval Roth <yuvalroth123@gmail.com>
` Re: Version 18.0 of postgres image in dockerhub - container crashes when starting up
2025-10-22 17:20 UTC Markus KARG <markus@headcrashing.eu>
[2+ messages in thread]
Re: PG17.6 wal apply bug (SIGSEGV)
2025-10-20 16:34 UTC badfilez@gmail.com <badfilez@gmail.com>
` Re: PG17.6 wal apply bug (SIGSEGV)
2025-10-20 17:18 UTC Peter Geoghegan <pg@bowt.ie>
` Re: PG17.6 wal apply bug (SIGSEGV)
2025-10-22 06:19 UTC badfilez@gmail.com <badfilez@gmail.com>
` Re: PG17.6 wal apply bug (SIGSEGV)
2025-10-22 08:44 UTC badfilez@gmail.com <badfilez@gmail.com>
` Re: PG17.6 wal apply bug (SIGSEGV)
2025-10-22 17:01 UTC Peter Geoghegan <pg@bowt.ie>
[5+ messages in thread]
postgres access violation in pg_detoast_datum
2025-10-21 06:49 UTC Arnd Empting <arnd.empting@koerber.com>
` Re: postgres access violation in pg_detoast_datum
2025-10-21 07:05 UTC David Rowley <dgrowleyml@gmail.com>
` Re: postgres access violation in pg_detoast_datum
2025-10-21 08:21 UTC Álvaro Herrera <alvherre@kurilemu.de>
[3+ messages in thread]
Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-05 08:55 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-05 10:06 UTC Markus KARG <markus@headcrashing.eu>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-05 10:51 UTC Thom Brown <thom@linux.com>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-05 19:57 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-05 20:22 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 09:55 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 10:40 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 14:20 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 14:34 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 16:09 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 16:13 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 16:17 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 16:21 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 17:01 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 17:09 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 17:29 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 20:41 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-06 21:39 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 07:15 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 07:34 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 09:50 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 19:34 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 19:49 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 19:56 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 20:04 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 21:38 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 22:13 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 23:03 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-07 23:17 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 07:49 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 10:04 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 12:13 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 13:04 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 13:07 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 17:46 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 19:08 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 20:09 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-08 20:22 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-09 07:40 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-10 10:03 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-10 21:26 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-10 21:30 UTC Andres Freund <andres@anarazel.de>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-10 21:36 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-12 08:24 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-19 20:37 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 01:33 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 09:34 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 11:22 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 14:42 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 19:09 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 20:02 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 21:06 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 21:57 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 22:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-20 22:46 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
2025-10-21 00:44 UTC David Rowley <dgrowleyml@gmail.com>
[56+ messages in thread]
PATCH for BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-09-18 08:44 UTC Алена Васильева <gorcom2012@gmail.com>
` Re: PATCH for BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-10-20 11:14 UTC Nikolay Shaplov <dhyan@nataraj.su>
[2+ messages in thread]
Re: PG17.6 zstd handling bug
2025-10-20 08:51 UTC badfilez@gmail.com <badfilez@gmail.com>
BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-05 05:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-06 03:42 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-06 03:59 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-06 06:22 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-06 06:49 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-06 10:44 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-06 12:04 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-17 07:05 UTC Andrew Bille <andrewbille@gmail.com>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-17 20:50 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-18 12:06 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-18 16:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
2025-10-20 02:30 UTC Dilip Kumar <dilipbalaut@gmail.com>
[12+ messages in thread]
Issues with blocksize smaller than 8KB
2025-10-17 15:42 UTC Casey Shobe <casey.allen.shobe@icloud.com>
` Re: Issues with blocksize smaller than 8KB
2025-10-18 16:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 14:44 UTC Casey & Gina <cg@osss.net>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 18:15 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 18:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 19:04 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 19:42 UTC Casey & Gina <cg@osss.net>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 20:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Issues with blocksize smaller than 8KB
2025-10-19 22:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-09 08:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-09 16:56 UTC Jeff Davis <pgsql@j-davis.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-10 01:34 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-12 08:10 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-14 15:51 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-14 21:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-15 14:21 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-15 22:45 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-15 22:51 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-16 01:10 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-16 03:29 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-16 04:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-16 05:04 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-16 19:40 UTC Jeff Davis <pgsql@j-davis.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 20:09 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 21:25 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 21:45 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 22:03 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 22:18 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 22:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-17 22:58 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-18 00:40 UTC Yuri Zamyatin <yuri@yrz.am>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-18 01:55 UTC Jeff Davis <pgsql@j-davis.com>
` Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
2025-10-18 03:11 UTC David Rowley <dgrowleyml@gmail.com>
[24+ messages in thread]
BUG #19089: Mounting Issue
2025-10-15 23:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19089: Mounting Issue
2025-10-16 16:45 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19089: Mounting Issue
2025-10-16 17:27 UTC Álvaro Herrera <alvherre@kurilemu.de>
[3+ messages in thread]
BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
2025-10-09 15:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
2025-10-09 17:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
2025-10-16 07:30 UTC 崔紫玉 <cuiziyu20@otcaix.iscas.ac.cn>
[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