agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedPostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-09-27 06:07 UTC Jacky Nguyen <nktpro@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-09-27 10:33 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-09-28 06:37 UTC shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-10-01 15:07 UTC rahul@rhyadav.dev
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-10-02 05:15 UTC shihao zhong <zhong950419@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-10-02 07:00 UTC rahul@rhyadav.dev
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-10-03 04:12 UTC shihao zhong <zhong950419@gmail.com>
[7+ messages in thread]
BUG #19628: Uninterruptible vacuum during hash index processing
2026-08-18 12:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-08-22 14:54 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-09-03 06:48 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-09-04 09:47 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-10-02 09:21 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-10-02 21:55 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-10-03 04:05 UTC shihao zhong <zhong950419@gmail.com>
[7+ messages in thread]
BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-25 19:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-26 09:02 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-26 09:31 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-26 14:26 UTC Nate Clark <natec425@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-10-02 18:20 UTC Nate Clark <natec425@gmail.com>
[5+ messages in thread]
BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-19 05:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-23 19:26 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-25 09:09 UTC Palak Chaturvedi <chaturvedipalak1911@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-25 15:38 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-27 15:08 UTC Palak Chaturvedi <chaturvedipalak1911@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-10-02 18:01 UTC Manu <manuelreyesbravo@gmail.com>
[6+ messages in thread]
Streaming decoding fails with "unexpected table_index_fetch_tuple call during logical decoding" when a relation has a TOASTed conbin (follow-up to BUG #18641)
2026-09-30 13:59 UTC Jiří Kavalík <jiri.kavalik@comgate.cz>
` Re: Streaming decoding fails with "unexpected table_index_fetch_tuple call during logical decoding" when a relation has a TOASTed conbin (follow-up to BUG #18641)
2026-10-02 07:33 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Streaming decoding fails with "unexpected table_index_fetch_tuple call during logical decoding" when a relation has a TOASTed conbin (follow-up to BUG #18641)
2026-10-02 08:29 UTC Jiří Kavalík <jiri.kavalik@comgate.cz>
[3+ messages in thread]
PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
2026-10-01 14:27 UTC Vladimir Savin <vladimir@encord.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
2026-10-01 16:15 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
2026-10-01 19:36 UTC Vladimir Savin <vladimir@encord.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
2026-10-02 08:04 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
2026-10-02 08:12 UTC Vladimir Savin <vladimir@encord.com>
[5+ messages in thread]
Backend crash (signal 11) in pg_trgm makesign() after ALTER TABLE ... SET STORAGE on a column with a gist_trgm_ops index
2026-10-02 03:22 UTC Thiago Bonfante <thiago@subbase.io>
` Re: Backend crash (signal 11) in pg_trgm makesign() after ALTER TABLE ... SET STORAGE on a column with a gist_trgm_ops index
2026-10-02 07:57 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
2026-10-01 18:29 UTC Samuel Olaoye <dapsalmy@gmail.com>
` Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
2026-10-02 07:47 UTC rahul@rhyadav.dev
[2+ messages in thread]
BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
2026-09-29 19:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
2026-10-02 03:17 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
2026-10-02 03:25 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
2026-10-02 03:49 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
2026-10-02 04:07 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19730: PostgreSQL `pg_backup_start` accepts newlines in the backup label, producing an unrestorable `backup
2026-10-02 04:32 UTC Michael Paquier <michael@paquier.xyz>
[6+ messages in thread]
autovacuum: automatically propagate updated parameters
2026-07-24 08:33 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 12:31 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 19:42 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 22:06 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 22:16 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 22:26 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-25 11:16 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 00:07 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 08:37 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 11:57 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 21:15 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 22:02 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 22:43 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 22:52 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-28 07:13 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-28 22:31 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-21 18:28 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 00:38 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 04:44 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 06:34 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 09:04 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 20:41 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 21:35 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 23:46 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 00:50 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 07:45 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 08:41 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 19:12 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 21:41 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 22:03 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-26 00:31 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-26 04:37 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-28 13:13 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-30 02:19 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-30 09:00 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-30 18:24 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-10-01 03:35 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-10-01 04:26 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-10-01 05:45 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-10-01 07:11 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-10-01 18:31 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[41+ messages in thread]
BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-08-02 17:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-04 08:01 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-26 16:54 UTC Rahul Yadav <rahul@rhyadav.com>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-29 08:37 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-30 10:07 UTC Rahul Yadav <rahul@rhyadav.com>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-30 23:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-10-01 03:18 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
[7+ messages in thread]
BUG #19728: A logical replication apply worker segfaults dereferencing a NULL `MyLogicalRepWorker->stream_filese
2026-09-29 15:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19728: A logical replication apply worker segfaults dereferencing a NULL `MyLogicalRepWorker->stream_filese
2026-10-01 03:09 UTC Ajin Cherian <itsajin@gmail.com>
[2+ messages in thread]
BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-19 17:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-21 23:49 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-22 12:12 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-22 12:37 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-23 03:43 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-23 17:51 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-24 02:43 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-24 06:22 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-25 04:29 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-26 00:09 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-28 07:01 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-28 17:37 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-29 06:06 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-30 05:30 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-30 07:48 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-10-01 03:04 UTC shihao zhong <zhong950419@gmail.com>
[16+ messages in thread]
BUG #19672: int8shl/int8shr Undefined Behavior on Out-of-Range Shift Amounts
2026-09-07 14:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19672: int8shl/int8shr Undefined Behavior on Out-of-Range Shift Amounts
2026-10-01 02:22 UTC David Rowley <dgrowleyml@gmail.com>
[2+ 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>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-30 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-30 18:20 UTC Jacob Champion <jacob.champion@enterprisedb.com>
[12+ messages in thread]
BUG #19727: pg-combinebackup fails to link
2026-09-29 14:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-29 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-29 14:56 UTC Ross Burton <ross@burtonini.com>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-29 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-29 16:45 UTC Ross Burton <ross@burtonini.com>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-30 11:10 UTC Ross Burton <ross@burtonini.com>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-30 13:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19727: pg-combinebackup fails to link
2026-09-30 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #19732: first_value/last_value/nth_value return NULL with EXCLUDE TIES when the current row is outside its f
2026-09-30 03:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19732: first_value/last_value/nth_value return NULL with EXCLUDE TIES when the current row is outside its f
2026-09-30 13:25 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19732: first_value/last_value/nth_value return NULL with EXCLUDE TIES when the current row is outside its f
2026-09-30 14:33 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[3+ messages in thread]
Possible G2-item at SERIALIZABLE
2026-05-22 16:44 UTC Kyle Kingsbury <aphyr@aphyr.com>
` Re: Possible G2-item at SERIALIZABLE
2026-05-30 18:47 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-05-31 13:19 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 01:49 UTC Kyle Kingsbury <aphyr@jepsen.io>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 06:18 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 10:11 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 22:00 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-06-02 08:18 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-02 23:03 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-06-17 17:39 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-08-19 17:24 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-08-20 11:17 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-08-26 21:33 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-08-27 06:56 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-09-30 12:31 UTC Aleksander Alekseev <aleksander@tigerdata.com>
[15+ messages in thread]
BUG #19734: NOT IN type resolution differs for outer Vars, producing different query results
2026-09-30 12:03 UTC PG Bug reporting form <noreply@postgresql.org>
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>
` Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
2026-09-30 09:43 UTC Rui Zhao <zhaorui126@gmail.com>
[6+ messages in thread]
Assertion failure in _bt_pagedel (leafblkno == scanblkno) after interrupted VACUUM
2026-09-28 19:30 UTC Iliia Khaprov <i.khaprov@gmail.com>
` Re: Assertion failure in _bt_pagedel (leafblkno == scanblkno) after interrupted VACUUM
2026-09-30 04:59 UTC shihao zhong <zhong950419@gmail.com>
` Re: Assertion failure in _bt_pagedel (leafblkno == scanblkno) after interrupted VACUUM
2026-09-30 06:14 UTC Iliia Khaprov <i.khaprov@gmail.com>
[3+ messages in thread]
REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-06-24 21:57 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-06-26 00:12 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-07-06 11:03 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-07-08 22:54 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-07-09 14:48 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-08-10 11:41 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-09-30 04:32 UTC Paul Kim <mok03127@gmail.com>
[7+ messages in thread]
BUG #19733: Row not visible to a new snapshot after its transactional logical decoding message has been streamed
2026-09-30 04:30 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19731: `first_value` returns an excluded peer for a nonempty `EXCLUDE TIES` frame
2026-09-29 19:16 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19729: Error de memoria compartida
2026-09-29 16:06 UTC PG Bug reporting form <noreply@postgresql.org>
[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