pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feed[PATCH v1] psql: schema-qualify catalog references in a tab-completion query
2026-07-09 12:23 UTC Vismay Tiwari <vismay.t@gmail.com>
` Re: [PATCH v1] psql: schema-qualify catalog references in a tab-completion query
2026-07-19 14:58 UTC Paul Kim <mok03127@gmail.com>
[2+ messages in thread]
BUG #19558: User-defined prefix operators "|" and "->" no longer parse in 19beta2 (SQL/PGQ grammar change)
2026-07-18 08:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:[patch] BUG #19558: User-defined prefix operators "|" and "->" no longer parse in 19beta2 (SQL/PGQ grammar change)
2026-07-18 15:38 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: [patch] BUG #19558: User-defined prefix operators "|" and "->" no longer parse in 19beta2 (SQL/PGQ grammar change)
2026-07-18 15:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [patch] BUG #19558: User-defined prefix operators "|" and "->" no longer parse in 19beta2 (SQL/PGQ grammar change)
2026-07-18 16:01 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: [patch] BUG #19558: User-defined prefix operators "|" and "->" no longer parse in 19beta2 (SQL/PGQ grammar change)
2026-07-18 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #19559: ALTER TABLE SET EXPRESSION / ALTER TYPE fails on columns referenced by a property graph
2026-07-18 11:21 UTC PG Bug reporting form <noreply@postgresql.org>
CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-15 13:05 UTC Maaz Syed Adeeb <maaz.adeeb@gmail.com>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-15 18:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-15 18:57 UTC Maaz Syed Adeeb <maaz.adeeb@gmail.com>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-15 19:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-16 05:20 UTC Maaz Syed Adeeb <maaz.adeeb@gmail.com>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-16 16:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-17 16:32 UTC Maaz Syed Adeeb <maaz.adeeb@gmail.com>
` Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
2026-07-17 17:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #19548: Missing dependency between a graph edge and the related PK
2026-07-08 14:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19548: Missing dependency between a graph edge and the related PK
2026-07-16 12:13 UTC Ayoub Kazar <kazarayoub2004@gmail.com>
` Re: BUG #19548: Missing dependency between a graph edge and the related PK
2026-07-17 14:25 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19548: Missing dependency between a graph edge and the related PK
2026-07-17 15:27 UTC Christophe Courtois <christophe.courtois@dalibo.com>
[4+ messages in thread]
Bug in heap_get_root_tuples
2026-07-15 13:37 UTC Konstantin Knizhnik <knizhnik@garret.ru>
` Re: Bug in heap_get_root_tuples
2026-07-16 00:29 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Bug in heap_get_root_tuples
2026-07-16 01:26 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Bug in heap_get_root_tuples
2026-07-16 22:57 UTC Peter Geoghegan <pg@bowt.ie>
[4+ messages in thread]
uuidv7 improperly accepts dates before 1970-01-01
2026-04-25 00:19 UTC Christophe Pettus <xof@thebuild.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-04-25 12:26 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-04-27 22:51 UTC Christophe Pettus <xof@thebuild.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-05-28 00:02 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-05-28 01:00 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-11 19:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-12 22:34 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 15:25 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 17:46 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 17:58 UTC Tristan Partin <tristan@partin.io>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 20:02 UTC Christophe Pettus <xof@thebuild.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 20:31 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 23:22 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-25 02:19 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-25 13:47 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-26 04:57 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-29 23:18 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-03 16:34 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-03 19:54 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-03 23:54 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-14 19:15 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-16 15:01 UTC Baji Shaik <baji.pgdev@gmail.com>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-16 19:23 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[23+ messages in thread]
BUG #19554: No match for argument: postgresql18-server Error: Unable to find a match: postgresql18-server
2026-07-16 15:23 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19547: `libpqrcv_create_slot` dereferences NULL on a malformed `CREATE_REPLICATION_SLOT` reply (just a sugg
2026-07-08 12:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-14 16:46 UTC Kenny Chen <kennychen851228@gmail.com>
` RE: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-15 04:33 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-15 11:51 UTC Kenny Chen <kennychen851228@gmail.com>
` Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-15 14:10 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-15 14:24 UTC Kenny Chen <kennychen851228@gmail.com>
` RE: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-16 00:36 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-16 04:45 UTC Fujii Masao <masao.fujii@gmail.com>
` RE: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-16 05:58 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply
2026-07-16 12:51 UTC Kenny Chen <kennychen851228@gmail.com>
[10+ messages in thread]
BUG #19382: Server crash at __nss_database_lookup
2026-01-20 05:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-01-20 09:15 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-01-20 09:25 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-01-20 09:47 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-01-23 01:18 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-01-24 01:55 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-01-26 22:04 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-02-02 21:45 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-02-26 23:55 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-16 22:09 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-19 05:00 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-19 07:53 UTC =?utf-8?B?c29uZ2ppbnpob3U=?= <tsinghualucky912@foxmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-20 18:16 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-02 11:18 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-02 23:14 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-04 12:42 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-09 04:24 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-14 23:49 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-16 12:00 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-16 23:20 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-17 06:57 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-23 04:17 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-06-02 23:44 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-06-30 20:50 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-06 22:16 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-07 23:20 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-13 20:53 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-13 22:18 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-15 22:16 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-16 06:23 UTC Zsolt Parragi <zsolt.parragi@percona.com>
[30+ messages in thread]
BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")
2026-07-10 07:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")
2026-07-13 10:33 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
` Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")
2026-07-13 13:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")
2026-07-13 13:13 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
[4+ messages in thread]
BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows
2026-06-30 07:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows
2026-07-01 08:40 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows
2026-07-13 06:09 UTC Karen Huang <karenhuang2017@gmail.com>
` Re: BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows
2026-07-13 07:21 UTC Karen Huang <karenhuang2017@gmail.com>
` Re: BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows
2026-07-13 10:01 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
[5+ messages in thread]
BUG #19549: Physical replication slot xmin value stuck
2026-07-09 08:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19549: Physical replication slot xmin value stuck
2026-07-10 23:23 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
[2+ messages in thread]
BUG #19507: Auto-named partition table constraint conflicts
2026-06-04 07:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-06-05 12:56 UTC Chengpeng Yan <chengpeng_yan@Outlook.com>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-06-05 13:01 UTC Marko Grujic <markoog@gmail.com>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-06-05 13:08 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-06-05 13:11 UTC Marko Grujic <markoog@gmail.com>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-07-09 09:15 UTC Vismay Tiwari <vismay.t@gmail.com>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-07-09 09:31 UTC Vismay Tiwari <vismay.t@gmail.com>
[7+ messages in thread]
BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-24 15:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-27 19:22 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-28 09:59 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-28 23:34 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-30 08:35 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-07-07 07:38 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-07-08 20:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[7+ messages in thread]
BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-06 13:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-06 17:01 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-08 18:25 UTC surya poondla <suryapoondla4@gmail.com>
[3+ messages in thread]
BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-03 13:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-05 08:20 UTC vaibhave postgres <postgresvaibhave@gmail.com>
` Re: BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-08 07:51 UTC Peter Eisentraut <peter@eisentraut.org>
[3+ messages in thread]
EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-02 16:58 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-02 22:10 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-03 03:06 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-03 08:36 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-06 02:17 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-07 13:49 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-07 14:20 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-08 00:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-08 00:42 UTC Thom Brown <thom@linux.com>
[9+ messages in thread]
BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-24 14:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-27 16:53 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-29 00:39 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-29 13:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 03:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 09:09 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 09:11 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 23:57 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-05 10:44 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-05 12:54 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-06 07:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-06 08:31 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 05:11 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 05:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 12:02 UTC David Rowley <dgrowleyml@gmail.com>
[15+ messages in thread]
BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-03 22:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:27 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:34 UTC Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:39 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 12:12 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-24 09:47 UTC Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-07-07 01:37 UTC Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-07-07 10:02 UTC Matheus Alcantara <matheusssilv97@gmail.com>
[8+ messages in thread]
BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2025-04-04 03:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-06-11 03:31 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-06-11 04:29 UTC TAKATSUKA Haruka <harukat@sraoss.co.jp>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-01 14:30 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-03 02:25 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-06 17:22 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-06 23:22 UTC Fujii Masao <masao.fujii@gmail.com>
[7+ messages in thread]
BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 07:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 14:41 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 18:19 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-07-05 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19543: ALTER RULE ... RENAME accepts reserved name "_RETURN" for a non-view rule; breaks a restored dump
2026-07-03 23:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19543: ALTER RULE ... RENAME accepts reserved name "_RETURN" for a non-view rule; breaks a restored dump
2026-07-04 14:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-16 11:29 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-17 19:19 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-18 05:24 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 14:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 15:43 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 17:46 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 23:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 08:40 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 13:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 16:48 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 17:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 19:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
Autoprewarm workers terminated due to a segmentation fault
2026-06-09 18:37 UTC Glauber Batista <glauberrbatista@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 21:06 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 21:44 UTC Tomas Vondra <tomas@vondra.me>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 22:25 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-11 14:40 UTC Tomas Vondra <tomas@vondra.me>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-15 14:35 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-26 17:55 UTC Tomas Vondra <tomas@vondra.me>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-26 18:07 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-29 15:12 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-07-01 19:16 UTC Glauber Batista <glauberrbatista@gmail.com>
[10+ 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