pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
The memory usage is positively correlated with the number of partition tables when pg_get_expr is called.
2025-08-20 06:16 UTC Zhu Yang <fairyfar@msn.com>
` Re: The memory usage is positively correlated with the number of partition tables when pg_get_expr is called.
2025-08-20 12:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19025: PostgreSQL log is not rotated
2025-08-19 10:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19025: PostgreSQL log is not rotated
2025-08-19 13:41 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #19025: PostgreSQL log is not rotated
2025-08-19 20:30 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19025: PostgreSQL log is not rotated
2025-08-20 11:19 UTC hubert depesz lubaczewski <depesz@depesz.com>
[4+ messages in thread]
BUG #19024: Error when trying to use pg_dump of new server on old server
2025-08-19 07:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19024: Error when trying to use pg_dump of new server on old server
2025-08-19 12:54 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19024: Error when trying to use pg_dump of new server on old server
2025-08-19 13:04 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19024: Error when trying to use pg_dump of new server on old server
2025-08-19 14:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
2025-07-06 11:06 UTC Ben Caspi <benc@aidoc.com>
` Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
2025-07-07 12:20 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
2025-07-09 12:40 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
2025-07-10 01:54 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
2025-07-13 10:52 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
2025-08-19 10:35 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[6+ messages in thread]
Error pg_upgrade version 11 to 15
2025-08-18 14:41 UTC IVAN HUMANES CABANAS (Fujitsu) <ivan.humanescabanas@fujitsu.com>
` Re: Error pg_upgrade version 11 to 15
2025-08-18 16:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error pg_upgrade version 11 to 15
2025-08-18 19:16 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Error pg_upgrade version 11 to 15
2025-08-18 20:07 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Error pg_upgrade version 11 to 15
2025-08-18 20:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error pg_upgrade version 11 to 15
2025-08-18 21:53 UTC Nathan Bossart <nathandbossart@gmail.com>
[6+ messages in thread]
BUG #19023: Table DDL default column expression depending on temp objects
2025-08-18 13:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19023: Table DDL default column expression depending on temp objects
2025-08-18 14:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19022: Trying to set up pem server not accepting any passwords
2025-08-17 18:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19022: Trying to set up pem server not accepting any passwords
2025-08-18 06:24 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #19021: Memory leak of SMgrRelation object during standby redo
2025-08-17 16:41 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join
2025-08-16 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join
2025-08-16 14:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
2025-08-11 22:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
2025-08-13 04:45 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
2025-08-13 15:53 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
2025-08-14 03:14 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
2025-08-14 09:22 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree
2025-08-16 12:07 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
[6+ messages in thread]
Empty query_id in pg_stat_activity
2025-08-13 09:50 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
` Re: Empty query_id in pg_stat_activity
2025-08-14 11:09 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
BUG #19019: Feature Request: allow the use of column reference in DEFAULT expression
2025-08-13 11:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19019: Feature Request: allow the use of column reference in DEFAULT expression
2025-08-13 13:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19019: Feature Request: allow the use of column reference in DEFAULT expression
2025-08-14 04:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
=?gb2312?B?tPC4tDogRW1wdHkgcXVlcnlfaWQgaW4gcGdfc3RhdF9hY3Rpdml0eQ==?=
2025-08-13 09:52 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
Nested comparison semantics are unpredictable
2025-08-12 16:16 UTC Richard Wesley <richard@duckdblabs.com>
` Re: Nested comparison semantics are unpredictable
2025-08-12 18:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size
2025-08-11 17:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size
2025-08-11 18:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
2025-08-07 07:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
2025-08-07 13:30 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
2025-08-07 21:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
2025-08-11 09:09 UTC 양주희 <1986comatose@gmail.com>
[4+ messages in thread]
BUG #18991: NUMA test fails on machine with two NUMA nodes when building 18beta2
2025-07-19 09:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18991: NUMA test fails on machine with two NUMA nodes when building 18beta2
2025-08-10 10:54 UTC Maximilian Bosch <maximilian@mbosch.me>
[2+ 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