agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19692: Generic partition-pruning plan delays statement_timeout cancellation
2026-09-17 08:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19692: Generic partition-pruning plan delays statement_timeout cancellation
2026-09-17 22:40 UTC Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
` Re: BUG #19692: Generic partition-pruning plan delays statement_timeout cancellation
2026-09-18 03:58 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 11:22 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 11:28 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 21:28 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 21:34 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-15 02:55 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-15 21:42 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-16 08:27 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-16 22:16 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-16 22:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-17 22:24 UTC Daniel Gustafsson <daniel@yesql.se>
[10+ messages in thread]
BUG #19691: Wrong configuration in .../Postgres/var-19/postgresql.auto.conf
2026-09-16 10:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19691: Wrong configuration in .../Postgres/var-19/postgresql.auto.conf
2026-09-16 12:05 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19691: Wrong configuration in .../Postgres/var-19/postgresql.auto.conf
2026-09-16 14:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19691: Wrong configuration in .../Postgres/var-19/postgresql.auto.conf
2026-09-16 15:42 UTC Jürgen Schmidt <jsschmidthb@gmail.com>
[4+ messages in thread]
Erro ao instalar PostgreSQL
2026-09-16 11:01 UTC Rikinho Melo <kingluxrikinho996@gmail.com>
BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-08-20 03:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-08-20 20:34 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-08-21 01:54 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-08-21 05:01 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-09 22:39 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-10 00:10 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-10 05:36 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-10 07:56 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-10 21:54 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-11 01:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-11 05:06 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-12 13:57 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-12 14:22 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-14 08:24 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-15 01:48 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-15 13:05 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-15 23:05 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-16 00:19 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-16 10:15 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
2026-09-16 10:25 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[20+ messages in thread]
BUG #19689: MERGE INSERT accepts a set-returning function during PREPARE but fails at EXECUTE
2026-09-15 06:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19689: MERGE INSERT accepts a set-returning function during PREPARE but fails at EXECUTE
2026-09-16 02:56 UTC Tender Wang <tndrwang@gmail.com>
[2+ messages in thread]
Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
2026-09-03 17:10 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
2026-09-03 17:20 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
2026-09-03 17:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
2026-09-03 18:30 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
2026-09-15 18:51 UTC Jacob Champion <jacob.champion@enterprisedb.com>
[5+ messages in thread]
REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-07-21 10:22 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-07-27 11:05 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-07-27 21:20 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-07-28 06:16 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-07-28 09:37 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-13 21:37 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-25 19:48 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-26 06:28 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-26 07:31 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-26 08:25 UTC Ewan Young <kdbase.hack@gmail.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-31 21:34 UTC Christophe Pettus <xof@thebuild.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-08-31 23:08 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-01 00:43 UTC Christophe Pettus <xof@thebuild.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-07 03:13 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-08 07:25 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-10 09:24 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-13 12:27 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-14 02:35 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-14 14:02 UTC Robert Treat <rob@xzilla.net>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-15 15:30 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
2026-09-15 18:30 UTC Robert Treat <rob@xzilla.net>
[21+ messages in thread]
BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
2026-08-19 03:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
2026-08-19 10:46 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
2026-08-21 10:15 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
2026-09-12 09:15 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
2026-09-12 15:50 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
2026-09-14 16:44 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[6+ messages in thread]
BUG #19680: FK integrity bypassed by session timezone (orphan rows)
2026-09-08 06:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19680: FK integrity bypassed by session timezone (orphan rows)
2026-09-14 15:39 UTC sahil mahajan <sahilmahajanstar@gmail.com>
` Re: BUG #19680: FK integrity bypassed by session timezone (orphan rows)
2026-09-14 16:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #19685: START_REPLICATION accepts an overflowing LSN component
2026-09-12 15:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19685: START_REPLICATION accepts an overflowing LSN component
2026-09-13 03:25 UTC Samriddha Kumar Tripathi <sumitkumartripathi0@gmail.com>
` Re: BUG #19685: START_REPLICATION accepts an overflowing LSN component
2026-09-13 04:48 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[3+ messages in thread]
BUG #19620: pg_class index corruption caused by statement_timeout during VACUUM FULL
2026-08-15 02:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19620: pg_class index corruption caused by statement_timeout during VACUUM FULL
2026-08-16 16:01 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19620: pg_class index corruption caused by statement_timeout during VACUUM FULL
2026-08-17 02:20 UTC Zheng Hacker <hackerzheng666@gmail.com>
` Re: BUG #19620: pg_class index corruption caused by statement_timeout during VACUUM FULL
2026-09-12 18:51 UTC Tesla V. <maah.celo.v@gmail.com>
[4+ messages in thread]
BUG #19681: ILIKE rejected on nondeterministic collations while LIKE works
2026-09-08 07:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19681: ILIKE rejected on nondeterministic collations while LIKE works
2026-09-12 15:50 UTC Nitin Motiani <nitinmotiani@google.com>
[2+ messages in thread]
BUG #19683: Can a stale postmaster.pid affect connections after PostgreSQL has already started successfully?
2026-09-10 20:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19683: Can a stale postmaster.pid affect connections after PostgreSQL has already started successfully?
2026-09-11 15:16 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #19682: Unable to drop a user with default privileges revoked
2026-09-09 09:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19682: Unable to drop a user with default privileges revoked
2026-09-10 13:49 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19682: Unable to drop a user with default privileges revoked
2026-09-11 07:45 UTC Sylvain PERRAUD <ext.solutec.sperraud@grandlyon.com>
` Re: BUG #19682: Unable to drop a user with default privileges revoked
2026-09-11 15:11 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-06-18 07:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-09 10:13 UTC Vismay Tiwari <vismay.t@gmail.com>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-10 04:49 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-10 05:51 UTC Vismay Tiwari <vismay.t@gmail.com>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-17 14:28 UTC Paul Kim <mok03127@gmail.com>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-09-10 15:33 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-09-11 09:29 UTC Fujii Masao <masao.fujii@gmail.com>
[7+ messages in thread]
pg_restore_attribute_stats accepts and persists null_frac=NaN
2026-09-08 09:53 UTC =?utf-8?B?4pmCz4DiiYwyNjIxOA==?= <1991230470@qq.com>
` Re: pg_restore_attribute_stats accepts and persists null_frac=NaN
2026-09-11 08:00 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
START_REPLICATION silently truncates an overlong LSN component
2026-09-08 09:58 UTC =?utf-8?B?4pmCz4DiiYwyNjIxOA==?= <1991230470@qq.com>
` Re: START_REPLICATION silently truncates an overlong LSN component
2026-09-10 13:41 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` RE: START_REPLICATION silently truncates an overlong LSN component
2026-09-11 02:35 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[3+ messages in thread]
BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
2026-09-07 14:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
2026-09-10 12:42 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
2026-09-10 16:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
2026-09-10 17:16 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
2026-09-10 17:22 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
2026-09-10 20:23 UTC Daniel Gustafsson <daniel@yesql.se>
[6+ messages in thread]
Hunspell AF alias count silently wraps to a smaller value
2026-09-08 09:50 UTC =?utf-8?B?4pmCz4DiiYwyNjIxOA==?= <1991230470@qq.com>
` Re: Hunspell AF alias count silently wraps to a smaller value
2026-09-10 13:28 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
unexpected behaviour generating queryid
2026-09-10 09:47 UTC mailinglists <lists@database.one>
[PATCH] Fail REPACK in presence of !isready !indvalid indexes
2026-09-10 08:49 UTC Álvaro Herrera <alvherre@kurilemu.de>
BUG #19664: nbtree: Assertion failure when a custom index AM reuses bthandler
2026-09-07 11:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19664: nbtree: Assertion failure when a custom index AM reuses bthandler
2026-09-09 09:59 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19664: nbtree: Assertion failure when a custom index AM reuses bthandler
2026-09-10 06:30 UTC Jingtang Zhang <mrdrivingduck@gmail.com>
[3+ messages in thread]
BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-05-18 05:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-05-20 13:06 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-07 10:53 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-07 15:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-11 05:49 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-12 16:22 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-19 06:25 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-19 07:40 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-20 21:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-21 05:47 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 05:44 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 06:07 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 17:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 18:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-23 08:32 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 06:14 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 09:56 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 12:19 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-25 07:55 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-25 10:44 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-25 13:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-26 05:18 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-26 06:56 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-26 08:30 UTC Laurenz Albe <laur@aon.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-02 21:09 UTC Laurenz Albe <laur@aon.at>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-10 07:00 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-10 17:37 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-26 16:28 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-26 17:25 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-08-02 09:41 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-08-10 16:48 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-09-04 07:00 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-09-09 16:29 UTC Rui Zhao <zhaorui126@gmail.com>
[34+ messages in thread]
table_rewrite event trigger can corrupt rows by inserting into the table being rewritten (20devel)
2026-09-08 10:12 UTC =?GBK?B?wre5+sfs?= <njuptlgq@163.com>
` Re: table_rewrite event trigger can corrupt rows by inserting into the table being rewritten (20devel)
2026-09-08 10:37 UTC Luguoqing <njuptlgq@163.com>
` Re: table_rewrite event trigger can corrupt rows by inserting into the table being rewritten (20devel)
2026-09-08 12:20 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: table_rewrite event trigger can corrupt rows by inserting into the table being rewritten (20devel)
2026-09-09 07:27 UTC Luguoqing <njuptlgq@163.com>
[4+ messages in thread]
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox