pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table
2025-10-02 16:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table
2025-10-10 03:01 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table
2025-10-10 11:03 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re:Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table
2025-10-10 17:14 UTC ocean_li_996 <ocean_li_996@163.com>
` Re:Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on ahash partition table
2025-10-11 02:00 UTC =?utf-8?B?c29uZ2ppbnpob3U=?= <tsinghualucky912@foxmail.com>
` Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on ahash partition table
2025-10-11 08:02 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on ahashpartition table
2025-10-11 10:19 UTC =?utf-8?B?c29uZ2ppbnpob3U=?= <tsinghualucky912@foxmail.com>
` Re: Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table
2025-10-11 18:34 UTC Álvaro Herrera <alvherre@kurilemu.de>
[8+ messages in thread]
Date/Time parsing of ISO 8601 timestamps with commas
2025-10-09 23:43 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: Date/Time parsing of ISO 8601 timestamps with commas
2025-10-10 20:09 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Date/Time parsing of ISO 8601 timestamps with commas
2025-10-10 20:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Date/Time parsing of ISO 8601 timestamps with commas
2025-10-10 20:45 UTC Zane Duffield <duffieldzane@gmail.com>
[4+ messages in thread]
BUG #19082: Failing assert in index scan
2025-10-10 09:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 11:14 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 15:40 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 16:12 UTC Matthijs van der Vleuten <postgresql@zr40.nl>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 16:28 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 17:09 UTC Matthijs van der Vleuten <postgresql@zr40.nl>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 18:10 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #19082: Failing assert in index scan
2025-10-10 18:22 UTC Peter Geoghegan <pg@bowt.ie>
[8+ messages in thread]
BUG #19076: Generic query plan is extremely slow
2025-10-07 20:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19076: Generic query plan is extremely slow
2025-10-08 08:21 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19076: Generic query plan is extremely slow
2025-10-08 09:13 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19076: Generic query plan is extremely slow
2025-10-08 11:17 UTC Premal Patel <premal.patel@veeva.com>
` Re: BUG #19076: Generic query plan is extremely slow
2025-10-08 11:41 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19076: Generic query plan is extremely slow
2025-10-10 09:56 UTC Andrei Lepikhov <lepihov@gmail.com>
[6+ messages in thread]
BUG #19079: can't dowmload documentation download aborted
2025-10-09 11:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19079: can't dowmload documentation download aborted
2025-10-09 12:05 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-05-15 05:33 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-05-15 14:26 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-05-15 15:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-05-15 16:21 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-05-16 12:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-17 09:58 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-17 15:05 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-17 15:49 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-17 15:55 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-28 06:20 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-28 20:41 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-29 05:49 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-30 18:45 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-30 18:58 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-30 19:16 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-30 19:48 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-30 19:50 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-30 20:14 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 02:39 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 02:49 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 03:00 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 20:03 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 20:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 21:04 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 21:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 21:40 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 21:59 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-07-31 22:12 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-01 21:47 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-02 01:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-02 02:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-02 03:07 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-04 20:11 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-04 22:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-05 00:14 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-05 02:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-05 05:31 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-05 14:47 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-07 17:58 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-08 22:03 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-11 14:01 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-11 18:44 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-12 04:43 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-12 04:46 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-21 01:48 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-21 02:58 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-08-25 12:30 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-09-25 18:07 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-09-25 18:45 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-09-25 19:28 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-09-25 19:46 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-09-26 12:30 UTC Todd Cook <cookt@blackduck.com>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-09-26 17:02 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
2025-10-07 06:10 UTC Sajith Prabhakar Shetty <ssajith@blackduck.com>
[54+ messages in thread]
BUG #19075: pg_upgradecluster does not copy conf.d/* during cluster upgrade
2025-10-06 17:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19075: pg_upgradecluster does not copy conf.d/* during cluster upgrade
2025-10-06 18:04 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
2025-10-05 02:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
2025-10-05 14:47 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
2025-10-05 15:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
=?gb18030?B?u9i4tKO6QlVHICMxOTA3MzogdGhlcmUgYXJlIG1l?= =?gb18030?B?YW5pbmdsZXNzIGNvZGUgaW4gX1NQSV9leGVjdXRl?= =?gb18030?B?X3BsYW4oKSB3aGVuIGNhblNldFRhZyBpcyB0cnVl?=
2025-10-05 10:05 UTC =?gb18030?B?d2ViYm9oYW4=?= <webbohan@qq.com>
BUG #19072: New-style SQL language function referencing a temp table behaves oddly
2025-10-04 16:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19072: New-style SQL language function referencing a temp table behaves oddly
2025-10-04 17:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19072: New-style SQL language function referencing a temp table behaves oddly
2025-10-04 20:02 UTC Bernice Southey <bernice.southey@gmail.com>
[3+ messages in thread]
BUG #19071: commit b448f1c8d broke LEFT JOIN pushdown
2025-10-03 10:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19071: commit b448f1c8d broke LEFT JOIN pushdown
2025-10-03 18:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19069: pg_advisory_xact_lock() in a WITH query doesn't work
2025-10-02 13:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19069: pg_advisory_xact_lock() in a WITH query doesn't work
2025-10-02 20:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #19069: pg_advisory_xact_lock() in a WITH query doesn't work
2025-10-03 09:34 UTC Maciej Walczak <m.walczak@megavision.pl>
[3+ messages in thread]
[Bug] Usage of stale dead_items pointer in parallel vacuum
2025-10-01 15:55 UTC Kevin Oommen Anish <kevin.o@zohocorp.com>
` Re: [Bug] Usage of stale dead_items pointer in parallel vacuum
2025-10-02 04:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [Bug] Usage of stale dead_items pointer in parallel vacuum
2025-10-02 05:09 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Bug] Usage of stale dead_items pointer in parallel vacuum
2025-10-02 09:33 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [Bug] Usage of stale dead_items pointer in parallel vacuum
2025-10-03 09:28 UTC John Naylor <johncnaylorls@gmail.com>
[5+ messages in thread]
BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-09-24 11:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-09-24 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-09-28 23:47 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-10-01 10:46 UTC Peter Dyballa <Peter_Dyballa@Web.DE>
` Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-10-02 00:08 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-10-02 01:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate
2025-10-02 19:53 UTC Peter Dyballa <Peter_Dyballa@Web.DE>
[7+ messages in thread]
BUG #19068: postgresql-server-dev-17 from apt.postgresql.org installs libpq-int.h for 18 version
2025-10-02 11:08 UTC PG Bug reporting form <noreply@postgresql.org>
IN List operator , where list of values are over a number of lines
2025-10-01 15:12 UTC White, Ian Keith <Ian.White@ncratleos.com>
` Re: IN List operator , where list of values are over a number of lines
2025-10-01 18:16 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: IN List operator , where list of values are over a number of lines
2025-10-02 08:32 UTC White, Ian Keith <Ian.White@ncratleos.com>
[3+ messages in thread]
BUG #15985: Hhhhhhh
2019-08-30 20:08 UTC PG Bug reporting form <noreply@postgresql.org>
` [PATCH] Update vacrel->dead_items alias ptr to point to the shared TidStore in parallel_vacuum after reallocation of shared TidStore.
2025-10-01 10:54 UTC Kevin Oommen Anish <kevin.o@zohocorp.com>
[2+ messages in thread]
Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-09-30 08:56 UTC Erki Eessaar <erki.eessaar@taltech.ee>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-09-30 11:36 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-09-30 12:12 UTC Erki Eessaar <erki.eessaar@taltech.ee>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-10-01 05:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-10-01 09:34 UTC Erki Eessaar <erki.eessaar@taltech.ee>
[5+ messages in thread]
Revoke role membership does not remove cascade privileges
2025-10-01 09:32 UTC Virender Singla <virender.cse@gmail.com>
Cast to regrole on a literal string in a PL/pgSQL function
2025-09-29 12:36 UTC LEMAIRE Leslie (Chargée de mission) - SG/DNUM/UNI/DRC <leslie.lemaire@developpement-durable.gouv.fr>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-29 17:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-29 22:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-30 09:25 UTC LEMAIRE Leslie (Chargée de mission) - SG/DNUM/UNI/DRC <leslie.lemaire@developpement-durable.gouv.fr>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-30 15:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-26 19:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-27 09:07 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-29 15:28 UTC Todd Cook <cookt@blackduck.com>
` Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-29 15:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
The issue of incorrect width estimation in UNION queries
2025-09-24 06:13 UTC =?gb18030?B?c3Vudy5mbnN0?= <936739278@qq.com>
` Re: The issue of incorrect width estimation in UNION queries
2025-09-24 10:47 UTC David Rowley <dgrowleyml@gmail.com>
` Re: The issue of incorrect width estimation in UNION queries
2025-09-25 21:42 UTC David Rowley <dgrowleyml@gmail.com>
` Re: The issue of incorrect width estimation in UNION queries
2025-09-29 01:50 UTC David Rowley <dgrowleyml@gmail.com>
[4+ messages in thread]
BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ?
2025-09-26 09:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ?
2025-09-26 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 07:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 12:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 12:59 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 13:35 UTC Anthony Sotolongo <asotolongo@gmail.com>
[4+ messages in thread]
BUG #19065: postgresql-18.0/src/bin/pg_combinebackup/reconstruct.c:230: Array sanity check in wrong place ?
2025-09-26 09:48 UTC PG Bug reporting form <noreply@postgresql.org>
[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