pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedTRAP: 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]
BUG #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]
[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