pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2024-12-08 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2024-12-09 02:56 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2024-12-31 05:00 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2025-05-03 01:22 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2025-05-03 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
[5+ messages in thread]
[PATCH] Fix self-referencing foreign keys on partitioned tables
2025-05-01 11:14 UTC Álvaro Herrera <alvherre@kurilemu.de>
Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-27 20:51 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 06:17 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 13:05 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 13:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 21:53 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-29 05:00 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-30 21:43 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-30 23:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-30 23:53 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-05-01 00:27 UTC marcos sicat <marcos.sicat@atlasifs.com>
[10+ messages in thread]
Doubt in reset date style
2025-04-30 21:17 UTC Manav Kumar <mkumar@yugabyte.com>
` Re: Doubt in reset date style
2025-04-30 21:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Doubt in reset date style
2025-04-30 21:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-24 10:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-24 12:39 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 05:58 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 07:44 UTC bowenshi <zxwsbg@qq.com>
` RE: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 09:07 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 09:56 UTC bowenshi <zxwsbg@qq.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-28 05:07 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-03-27 11:49 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-17 05:34 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-18 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-22 00:56 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-23 11:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-07-04 15:43 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-07-05 01:23 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-09-19 08:15 UTC Alexander Pyhalov <a.pyhalov@postgrespro.ru>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2025-04-30 18:19 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2025-04-30 19:55 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[17+ messages in thread]
BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-27 16:15 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-27 17:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-27 18:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-29 11:57 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
2025-04-29 12:13 UTC =?utf-8?B?SmluaHVpIExhaQ==?= <jh.lai@qq.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
2025-04-29 12:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
2025-04-29 18:44 UTC Francisco Olarte <folarte@peoplecall.com>
[7+ messages in thread]
BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 16:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 17:34 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 17:54 UTC =?utf-8?B?6LWW6ZSm6L6J?= <jh.lai@qq.com>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 19:19 UTC Christophe Pettus <xof@thebuild.com>
[4+ messages in thread]
BUG #18906: EXCEPT with identical left/right queries isn't eliminated
2025-04-27 17:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18906: EXCEPT with identical left/right queries isn't eliminated
2025-04-27 17:37 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 05:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 06:51 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 07:00 UTC Никита Калинин <n.kalinin@postgrespro.ru>
` Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 07:15 UTC Dilip Kumar <dilipbalaut@gmail.com>
[4+ messages in thread]
BUG #18893: Segfault during analyze pg_database
2025-04-12 03:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-13 12:11 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-13 14:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-14 09:18 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-24 23:31 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
DSA refcnt overflow in pg_stat/could not attach to dynamic shared area
2025-04-24 06:04 UTC =?gb18030?B?wO7UsNSw?= <summer.li.yuan@qq.com>
` Re: DSA refcnt overflow in pg_stat/could not attach to dynamic shared area
2025-04-24 07:05 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
Disabled logical replication origin session causes primary key errors
2025-04-18 21:22 UTC Shawn McCoy <shawn.the.mccoy@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-20 05:53 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-21 05:17 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-21 10:08 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-21 16:17 UTC vignesh C <vignesh21@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-21 17:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 02:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-22 09:06 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 09:36 UTC vignesh C <vignesh21@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-22 11:00 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 13:37 UTC vignesh C <vignesh21@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 18:10 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 20:10 UTC Shawn McCoy <shawn.the.mccoy@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-23 01:41 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-23 09:01 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-23 15:58 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-24 02:25 UTC Michael Paquier <michael@paquier.xyz>
[17+ messages in thread]
Command order bug in pg_dump
2025-04-21 10:56 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-21 14:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-21 17:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-21 17:30 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-21 17:33 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-21 17:44 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Command order bug in pg_dump
2025-04-21 19:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-22 19:08 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: Command order bug in pg_dump
2025-04-22 19:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-22 20:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-23 02:59 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-23 13:01 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: Command order bug in pg_dump
2025-04-23 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-09 13:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-09 22:47 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-10 12:28 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-11 22:30 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-13 23:26 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-14 14:41 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-15 09:41 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-15 13:16 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-16 04:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-16 06:57 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-16 10:00 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-21 09:41 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-21 12:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-21 20:23 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-23 06:52 UTC Andrei Lepikhov <lepihov@gmail.com>
[15+ messages in thread]
PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-03-20 15:14 UTC Ben Caspi <benc@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-04 12:30 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-07 14:59 UTC Avi Uziel <avi.uziel@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-08 05:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-09 23:49 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-10 07:02 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-10 07:14 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 14:51 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 16:10 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 21:11 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 21:33 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-16 00:34 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-17 19:18 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-17 19:31 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-22 10:58 UTC Avi Uziel <avi.uziel@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-22 11:30 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-22 11:39 UTC Avi Uziel <avi.uziel@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-23 05:40 UTC Manika Singhal <manika.singhal@enterprisedb.com>
[18+ messages in thread]
BUG #18901: Bug in Perl-Script "src/backend/nodes/gen_node_support.pl"
2025-04-22 16:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18901: Bug in Perl-Script "src/backend/nodes/gen_node_support.pl"
2025-04-22 17:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18872: The current OS X version is not supported
2025-03-30 19:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18872: The current OS X version is not supported
2025-03-30 21:07 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18872: The current OS X version is not supported
2025-04-22 13:40 UTC Dave Cramer <davecramer@postgres.rocks>
[3+ messages in thread]
BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed
2025-04-22 09:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed
2025-04-22 12:27 UTC Robert Treat <rob@xzilla.net>
[2+ messages in thread]
ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-01-23 09:11 UTC Richard Guo <guofenglinux@gmail.com>
` Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-04-11 12:48 UTC Robins Tharakan <tharakan@gmail.com>
` Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-04-11 14:41 UTC Noah Misch <noah@leadboat.com>
` Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-04-21 04:06 UTC Noah Misch <noah@leadboat.com>
[4+ messages in thread]
Error when using array_agg with filter where clause in pg16 and pg17
2025-04-08 12:38 UTC Kaimeh <kkaimeh@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-08 15:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-08 23:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:43 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:54 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 01:50 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 02:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 02:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-20 10:21 UTC David Rowley <dgrowleyml@gmail.com>
[11+ messages in thread]
BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17)
2025-04-16 20:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17)
2025-04-19 19:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference to backtrace_symbols_fd
2025-04-18 12:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference to backtrace_symbols_fd
2025-04-18 17:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18898: replication process not working... sometimes
2025-04-17 00:09 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #18898: replication process not working... sometimes
2025-04-18 12:31 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[2+ messages in thread]
BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-12 02:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-12 19:19 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-12 19:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-13 13:09 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-13 14:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-14 08:55 UTC Gang Chen <gchen@s2now.com>
` Re: 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-16 16:43 UTC Bruce Momjian <bruce@momjian.us>
[7+ messages in thread]
BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 08:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 12:20 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 12:41 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 13:26 UTC Devrim Gündüz <devrim@gunduz.org>
[4+ 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