pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
BUG #19016: Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-08-08 07:09 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-04-30 11:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-05-08 12:55 UTC Robin Haberkorn <haberkorn@b1-systems.de>
` Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-08-08 07:08 UTC Алена Васильева <gorcom2012@gmail.com>
[3+ messages in thread]
BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 19:43 UTC Peter Praxmarer <ppraxmarer@gmail.com>
` Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 19:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 19:54 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 20:15 UTC Peter Praxmarer <ppraxmarer@gmail.com>
[4+ messages in thread]
BUG #19015: insert-returning failure: stable function in select policy doesn't see before-insert trigger change
2025-08-07 19:56 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-05 21:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-05 23:01 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 11:56 UTC dbman@sqlexec.com <dbman@sqlexec.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 14:53 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 15:42 UTC dbman@sqlexec.com <dbman@sqlexec.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 16:32 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 16:52 UTC dbman@sqlexec.com <dbman@sqlexec.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 18:04 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 18:34 UTC David G. Johnston <david.g.johnston@gmail.com>
[9+ messages in thread]
BUG #16961: Could not access status of transaction
2021-04-13 15:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16961: Could not access status of transaction
2021-04-14 16:11 UTC Stepan Yankevych <stepya@ukr.net>
` RE: BUG #16961: Could not access status of transaction
2021-04-19 18:49 UTC Stepan Yankevych <Stepan_Yankevych@epam.com>
` Re: BUG #16961: Could not access status of transaction
2021-06-05 20:55 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #16961: Could not access status of transaction
2021-06-05 21:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16961: Could not access status of transaction
2021-06-05 21:31 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #16961: Could not access status of transaction
2025-06-25 04:04 UTC Daniil Davydov <3danissimo@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-01 03:41 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-01 03:50 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-04 11:08 UTC Daniil Davydov <3danissimo@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-05 23:30 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-06 03:30 UTC Daniil Davydov <3danissimo@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-06 04:55 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
[13+ messages in thread]
CREATE DATABASE copies datlocale even if datlocprovider differs
2025-07-29 23:33 UTC Jeff Davis <pgsql@j-davis.com>
` Re: CREATE DATABASE copies datlocale even if datlocprovider differs
2025-08-05 16:28 UTC Jeff Davis <pgsql@j-davis.com>
[2+ messages in thread]
BUG #19008: Problems downloading metadata for dnf - probably missing private key (GPG signature)
2025-08-04 08:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19008: Problems downloading metadata for dnf - probably missing private key (GPG signature)
2025-08-05 14:40 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
AW: BUG #19011: repomd.xml.asc on postgresql 16 empty
2025-08-05 13:07 UTC Wehnert, Thomas <Thomas.Wehnert@uhb-software.com>
BUG #19012: GPG signature file for RHEL 9 is 0 bytes
2025-08-04 16:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19012: GPG signature file for RHEL 9 is 0 bytes
2025-08-05 12:57 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19011: repomd.xml.asc on postgresql 16 empty
2025-08-04 15:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19011: repomd.xml.asc on postgresql 16 empty
2025-08-05 12:56 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
pgdg 16 package repo failure from missing repomd.xml.asc
2025-08-04 02:44 UTC Jeff Palmer <darren1713@gmail.com>
` Re: pgdg 16 package repo failure from missing repomd.xml.asc
2025-08-04 23:32 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19010: Empty repomd.xml.asc file
2025-08-04 14:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19010: Empty repomd.xml.asc file
2025-08-04 23:31 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19009: Empty repomd.xml.asc file on pgdg16 mirror causes metadata retrieval failure
2025-08-04 12:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19009: Empty repomd.xml.asc file on pgdg16 mirror causes metadata retrieval failure
2025-08-04 23:31 UTC Devrim Gündüz <devrim@gunduz.org>
[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