pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-08-28 12:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-04 09:03 UTC Yushu Chen <gentcys@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-04 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-05 12:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-05 12:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-05 14:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 15:34 UTC Katja Henke <katja.henke@foo.ag>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 21:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 21:58 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 22:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 22:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-08 08:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-08 15:10 UTC David G. Johnston <david.g.johnston@gmail.com>
[13+ messages in thread]
AW: BUG #19043: jdbc connection url is not case insensitive
2025-09-08 06:39 UTC Kristo Marijo <M.Kristo@rewe-group.at>
Broken PQtrace CopyData display
2025-08-29 19:45 UTC Ran Benita <ran@unusedvar.com>
` Re: Broken PQtrace CopyData display
2025-08-31 04:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: Broken PQtrace CopyData display
2025-09-03 03:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: Broken PQtrace CopyData display
2025-09-06 08:42 UTC Álvaro Herrera <alvherre@kurilemu.de>
[4+ messages in thread]
BUG #19043: jdbc connection url is not case insensitive
2025-09-05 06:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19043: jdbc connection url is not case insensitive
2025-09-05 21:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19043: jdbc connection url is not case insensitive
2025-09-05 21:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19043: jdbc connection url is not case insensitive
2025-09-06 00:41 UTC Greg Sabino Mullane <htamfids@gmail.com>
[4+ messages in thread]
BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-08-30 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-08-30 21:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-01 07:32 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-01 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-02 06:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-02 15:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 00:42 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 01:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 08:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 08:56 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-05 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
[11+ messages in thread]
BUG #19041: Logical replication locks wal processing
2025-09-03 10:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19041: Logical replication locks wal processing
2025-09-03 11:55 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19041: Logical replication locks wal processing
2025-09-03 12:10 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #19041: Logical replication locks wal processing
2025-09-03 12:45 UTC Dilip Kumar <dilipbalaut@gmail.com>
` RE: BUG #19041: Logical replication locks wal processing
2025-09-05 02:28 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[5+ messages in thread]
empty,query_id, pg_stat_activity
2025-09-02 09:25 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
` Re: empty,query_id, pg_stat_activity
2025-09-02 15:11 UTC Greg Sabino Mullane <htamfids@gmail.com>
` 答复: empty,query_id, pg_stat_activity
2025-09-03 02:00 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
` Re: empty,query_id, pg_stat_activity
2025-09-03 20:54 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: empty,query_id, pg_stat_activity
2025-09-04 00:25 UTC Michael Paquier <michael@paquier.xyz>
` Re: empty,query_id, pg_stat_activity
2025-09-04 12:56 UTC Greg Sabino Mullane <htamfids@gmail.com>
[6+ messages in thread]
Postgres immediately closing connection when `systemctl reboot` command is fired.
2025-09-04 08:59 UTC Raghvendra Mishra <raghshr1351@gmail.com>
=?gb2312?B?tPC4tDogZW1wdHkscXVlcnlfaWQsIHBnX3N0YXRfYWN0aXZpdHk=?=
2025-09-04 03:32 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-18 19:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-18 21:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-21 20:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-21 20:42 UTC Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-21 21:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 12:28 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 17:06 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 20:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
回复:Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-03 16:59 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
BUG #18459: running pg_ctl.exe from inside a program running as a Windows service returns "error code 6"
2024-05-09 18:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18459: running pg_ctl.exe from inside a program running as a Windows service returns "error code 6"
2025-09-02 15:57 UTC Martin Fernau <martin.fernau@fernausoft.de>
[2+ messages in thread]
BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-07 12:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 07:03 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 07:57 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 09:29 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 09:38 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 09:47 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 10:12 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 11:58 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 13:07 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-09 15:26 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2025-09-02 14:12 UTC Maxim Michkov <m.michkov@arenadata.io>
[11+ messages in thread]
BUG #19039: UNREACHABLE_CODE: Remove unreachable code in network_send - replace with assertion
2025-09-02 07:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19039: UNREACHABLE_CODE: Remove unreachable code in network_send - replace with assertion
2025-09-02 11:54 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
bug reapper: Empty query_id in pg_stat_activity
2025-08-28 09:22 UTC =?ISO-8859-1?B?ZHVvbWkucGVuZw==?= <duomi.peng@qq.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 11:07 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:09 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:25 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:28 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:42 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-31 05:02 UTC Michael Paquier <michael@paquier.xyz>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-09-01 16:38 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-09-02 04:59 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
[9+ messages in thread]
BUG #19031: pg_trgm infinite loop on certain cases
2025-08-25 21:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-26 00:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-26 11:26 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-26 15:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-27 08:33 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-27 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-27 19:17 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-31 22:13 UTC Alexander Korotkov <aekorotkov@gmail.com>
[8+ messages in thread]
BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-29 11:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-29 15:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 01:51 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 01:57 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 02:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 02:09 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[6+ messages in thread]
BUG #19033: Inconsistency between prepared statement and normal statement when cast bit to integer
2025-08-27 07:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19033: Inconsistency between prepared statement and normal statement when cast bit to integer
2025-08-27 14:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19033: Inconsistency between prepared statement and normal statement when cast bit to integer
2025-08-27 14:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-23 13:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 03:51 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 05:09 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 05:24 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 05:44 UTC Thadeus Anand <thadeus@rmkv.com>
` RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 08:05 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 08:16 UTC Thadeus Anand <thadeus@rmkv.com>
` RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 09:49 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 10:03 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 10:05 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 10:30 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 11:13 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-25 11:35 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-26 08:15 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-26 10:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-26 12:14 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-26 12:21 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 02:39 UTC Nantha kumar.T. <nanthad@gmail.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 03:29 UTC Thadeus Anand <thadeus@rmkv.com>
` RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 03:31 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 03:38 UTC Thadeus Anand <thadeus@rmkv.com>
` RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 03:39 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 04:36 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 05:31 UTC Thadeus Anand <thadeus@rmkv.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 06:30 UTC Nantha kumar.T. <nanthad@gmail.com>
` RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 07:21 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 07:37 UTC Thadeus Anand <thadeus@rmkv.com>
` RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 09:38 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
2025-08-27 09:49 UTC Thadeus Anand <thadeus@rmkv.com>
[29+ messages in thread]
BUG #19032: In restore_command %f parameter does not support WAL partial files.
2025-08-26 14:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19032: In restore_command %f parameter does not support WAL partial files.
2025-08-27 00:48 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19032: In restore_command %f parameter does not support WAL partial files.
2025-08-27 09:37 UTC Wojciech Szenajch <wszenajch@gmail.com>
[3+ messages in thread]
BUG #19030: Hash join leads to extremely high memory usage
2025-08-23 15:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19030: Hash join leads to extremely high memory usage
2025-08-23 22:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1
2025-08-21 04:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1
2025-08-21 05:03 UTC KAZAR Ayoub <ma_kazar@esi.dz>
` Re: BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1
2025-08-22 02:16 UTC Thomas Munro <thomas.munro@gmail.com>
[3+ messages in thread]
Unexpected Standby Shutdown on sync_replication_slots change
2025-07-24 13:54 UTC Hugo DUBOIS <hdubois@scaleway.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-24 15:55 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-24 18:50 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-25 06:16 UTC shveta malik <shveta.malik@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-25 09:39 UTC Hugo DUBOIS <hdubois@scaleway.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-25 10:32 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-25 12:13 UTC Hugo DUBOIS <hdubois@scaleway.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-25 16:01 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-25 16:21 UTC Hugo DUBOIS <hdubois@scaleway.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-28 04:48 UTC shveta malik <shveta.malik@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-28 09:55 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-29 04:40 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-29 06:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-07-30 03:15 UTC shveta malik <shveta.malik@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-02 04:28 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-04 11:59 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-05 05:08 UTC shveta malik <shveta.malik@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-20 10:16 UTC shveta malik <shveta.malik@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-21 02:11 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-21 04:29 UTC shveta malik <shveta.malik@gmail.com>
` Re: Unexpected Standby Shutdown on sync_replication_slots change
2025-08-21 13:22 UTC Fujii Masao <masao.fujii@gmail.com>
[21+ messages in thread]
BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-07-16 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-07-30 10:54 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-07-31 05:20 UTC Dilip Kumar <dilipbalaut@gmail.com>
` RE: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-07-31 09:03 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-07-31 11:44 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-07-31 11:59 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-04 03:37 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-04 03:59 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-04 12:28 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-04 12:50 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-04 13:38 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-05 06:21 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-06 04:58 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-06 05:37 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-06 06:08 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-07 13:48 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-13 05:46 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-13 05:50 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-13 09:30 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-14 06:09 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-14 08:35 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-14 08:48 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-14 11:02 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-14 11:34 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-15 06:21 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-15 06:28 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-17 13:53 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 03:04 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 03:34 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 06:06 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 07:25 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 09:26 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 14:21 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-18 16:41 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-19 02:54 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-19 09:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
2025-08-21 03:46 UTC Dilip Kumar <dilipbalaut@gmail.com>
[37+ messages in thread]
BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 11:21 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 11:43 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 13:24 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 13:34 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 14:56 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 15:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 16:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
2025-08-20 17:35 UTC Kirill Reshke <reshkekirill@gmail.com>
[9+ 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