pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedAutomating 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]
TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-05 18:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-06 11:30 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-07 03:38 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-07 17:29 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-07 23:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-08 07:15 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-18 06:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-18 07:02 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-18 08:42 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-19 00:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-19 18:04 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-22 10:59 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-08-22 20:53 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-17 10:42 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-18 00:24 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-23 21:41 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-23 23:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-24 10:28 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-24 16:45 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-24 23:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-25 10:55 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-26 13:34 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-09-28 08:55 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-01 10:53 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-02 11:01 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-02 22:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-03 00:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-03 11:00 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-03 21:21 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-05 17:15 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-06 03:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-07 10:59 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-07 17:25 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-08 00:05 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-08 06:09 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-09 02:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-12 18:05 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-13 20:18 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-14 04:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-15 08:22 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-15 18:35 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
2025-10-16 01:53 UTC Michael Paquier <michael@paquier.xyz>
[42+ messages in thread]
BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-14 08:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-14 08:15 UTC Andrew Bille <andrewbille@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-14 19:36 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-14 19:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-14 22:03 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-14 23:56 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 02:21 UTC Andrew Bille <andrewbille@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 08:56 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 09:10 UTC Andrew Bille <andrewbille@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 16:24 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 21:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 21:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 23:07 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-15 23:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-16 00:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-16 00:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-16 01:23 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-16 01:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-16 01:36 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
2025-10-16 01:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
[20+ messages in thread]
BUG #19080: CancelRequest message documentation bug
2025-10-09 13:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19080: CancelRequest message documentation bug
2025-10-10 03:16 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19080: CancelRequest message documentation bug
2025-10-14 02:06 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19080: CancelRequest message documentation bug
2025-10-14 11:39 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19080: CancelRequest message documentation bug
2025-10-15 02:30 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19080: CancelRequest message documentation bug
2025-10-15 08:09 UTC Magnus Hagander <magnus@hagander.net>
[6+ messages in thread]
order by alias - doesn't work sometimes?
2025-10-14 14:50 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: order by alias - doesn't work sometimes?
2025-10-14 15:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: order by alias - doesn't work sometimes?
2025-10-14 15:46 UTC hubert depesz lubaczewski <depesz@depesz.com>
[3+ messages in thread]
Logical replication fails when partition column order differs from parent
2025-10-13 12:07 UTC Вадим Ковтун <kovtunvadim@gmail.com>
` RE: Logical replication fails when partition column order differs from parent
2025-10-14 06:53 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[2+ messages in thread]
BUG #19085: Using EXECUTE to run a multi-statement SQL string causes an assertion failure
2025-10-14 03:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19085: Using EXECUTE to run a multi-statement SQL string causes an assertion failure
2025-10-14 05:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19084: dump/restore table doesn't work with GENARETED column and custom type and cast in function
2025-10-13 13:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19084: dump/restore table doesn't work with GENARETED column and custom type and cast in function
2025-10-13 15:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19084: dump/restore table doesn't work with GENARETED column and custom type and cast in function
2025-10-13 15:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #19083: Foreign inner join is the case for char() keys but not for varchar()
2025-10-13 12:18 UTC PG Bug reporting form <noreply@postgresql.org>
Potential deadlock in pgaio_io_wait()
2025-08-04 05:54 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Potential deadlock in pgaio_io_wait()
2025-08-04 06:34 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Potential deadlock in pgaio_io_wait()
2025-08-15 05:39 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Potential deadlock in pgaio_io_wait()
2025-08-19 00:07 UTC Andres Freund <andres@anarazel.de>
` Re: Potential deadlock in pgaio_io_wait()
2025-09-22 14:53 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Potential deadlock in pgaio_io_wait()
2025-10-10 01:44 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Potential deadlock in pgaio_io_wait()
2025-10-12 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
[7+ messages in thread]
BUG #11500: PRIMARY KEY index not being used
2014-09-26 08:02 UTC marko@joh.to
` Re: BUG #11500: PRIMARY KEY index not being used
2014-09-26 12:02 UTC Marti Raudsepp <marti@juffo.org>
` Re: BUG #11500: PRIMARY KEY index not being used
2014-09-26 12:54 UTC Marko Tiikkaja <marko@joh.to>
` Re: BUG #11500: PRIMARY KEY index not being used
2014-09-26 17:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-03 06:23 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-03 06:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-03 07:56 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-03 14:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-04 02:39 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-04 03:19 UTC David Rowley <dgrowleyml@gmail.com>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-04 04:00 UTC Wyatt Alt <wyatt.alt@gmail.com>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-04 17:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-05 00:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-05 06:38 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-05 06:41 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-05 18:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-06 10:38 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-06 11:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-10 14:52 UTC Marko Tiikkaja <marko@joh.to>
` Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
2025-10-12 08:24 UTC David Rowley <dgrowleyml@gmail.com>
[20+ messages in thread]
BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-02-28 11:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-02-29 06:21 UTC =?ISO-8859-1?B?ZmVpY2hhbmdob25n?= <feichanghong@qq.com>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-03-05 03:13 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-03-05 07:37 UTC alvherre <alvherre@alvh.no-ip.org>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-03-05 08:57 UTC 费长红 <feichanghong@qq.com>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-03-05 23:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-07-15 19:35 UTC alvherre <alvherre@alvh.no-ip.org>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-07-16 05:03 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-07-16 07:39 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2024-11-19 09:57 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
2025-10-11 18:35 UTC Álvaro Herrera <alvherre@kurilemu.de>
[11+ 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