public inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-20 21:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-21 07:07 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-21 07:12 UTC Marko Tiikkaja <marko@joh.to>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-21 07:25 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-21 07:45 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-21 08:34 UTC Radim Marek <radim@boringsql.com>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-21 09:06 UTC Radim Marek <radim@boringsql.com>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-22 16:51 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[8+ messages in thread]
Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 08:40 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 09:46 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 12:18 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 12:21 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 13:31 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 14:38 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-18 17:55 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-19 01:11 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-19 07:18 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-19 13:03 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-20 14:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-20 14:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-20 20:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-22 05:15 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-23 21:28 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-23 21:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-26 19:59 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-27 01:19 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-04-22 15:10 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-04-23 08:26 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-05-22 10:16 UTC Andrei Lepikhov <lepihov@gmail.com>
[21+ messages in thread]
BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
2026-05-20 09:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
2026-05-20 20:51 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
2026-05-21 20:51 UTC Andreas Karlsson <andreas@proxel.se>
[3+ messages in thread]
BUG #19469: Prevent SIGSEGV on FETCH after ALTER TYPE of cursor rowtype
2026-04-27 10:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19469: Prevent SIGSEGV on FETCH after ALTER TYPE of cursor rowtype
2026-05-21 20:13 UTC Matheus Alcantara <matheusssilv97@gmail.com>
[2+ messages in thread]
BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT
2026-05-18 07:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT
2026-05-21 18:41 UTC PetSerAl <petseral@gmail.com>
[2+ messages in thread]
BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-19 11:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-20 04:37 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-20 10:03 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-20 11:31 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-20 12:05 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-20 12:45 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-21 08:10 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-21 11:31 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always
2026-05-21 11:48 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[9+ messages in thread]
Fwd: Non-cancellable queries
2026-05-19 20:44 UTC Anton Fedorov <datacompboy@gmail.com>
` Re: Fwd: Non-cancellable queries
2026-05-20 10:55 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Fwd: Non-cancellable queries
2026-05-20 20:11 UTC Anton Fedorov <datacompboy@gmail.com>
` Re: Fwd: Non-cancellable queries
2026-05-20 20:16 UTC Anton Fedorov <datacompboy@gmail.com>
[4+ messages in thread]
BUG #19484: Segmentation fault triggered by FDW
2026-05-18 06:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-05-20 12:37 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-05-20 17:46 UTC Etsuro Fujita <etsuro.fujita@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>
[2+ messages in thread]
Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 13:47 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re[2]: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 14:05 UTC Глеб Борков <long76.git@mail.ru>
` Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 15:56 UTC Long76 <long76.git@mail.ru>
` BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-05-19 15:35 UTC David G. Johnston <david.g.johnston@gmail.com>
[4+ messages in thread]
Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 14:49 UTC Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 18:12 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 19:00 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 22:34 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 22:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-04 14:45 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-16 05:25 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-16 18:52 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-05-19 10:10 UTC Adrian Mönnich <adrian.moennich@cern.ch>
[9+ messages in thread]
BUG #19487: Error while executing SQL query involving XML parsing
2026-05-19 09:01 UTC PG Bug reporting form <noreply@postgresql.org>
Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-18 22:32 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-02 22:45 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-05 01:01 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-09 13:57 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-12 00:45 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-12 11:33 UTC =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-13 07:20 UTC =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-20 18:01 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-21 06:19 UTC =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-25 22:45 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-05-18 16:48 UTC surya poondla <suryapoondla4@gmail.com>
[11+ messages in thread]
BUG #19485: Compilation warnings and notes with GCC 16.1.1 on new Fedora 44
2026-05-18 07:06 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19481: multivariate MCV expression stats not applied for equivalent predicates on nullable side of LEFT JOI
2026-05-16 10:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19481: multivariate MCV expression stats not applied for equivalent predicates on nullable side of LEFT JOI
2026-05-18 06:40 UTC Andrei Lepikhov <lepihov@gmail.com>
[2+ messages in thread]
BUG #19478: `dblink_close` can be used for injection.
2026-05-15 01:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19478: `dblink_close` can be used for injection.
2026-05-16 01:24 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #19478: `dblink_close` can be used for injection.
2026-05-16 04:06 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19478: `dblink_close` can be used for injection.
2026-05-16 04:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19478: `dblink_close` can be used for injection.
2026-05-18 03:10 UTC Japin Li <japinli@hotmail.com>
[5+ messages in thread]
BUG #19462: MERGE on partitioned table with INSERT DEFAULT VALUES fails with "unknown action in MERGE WHEN clau
2026-04-20 09:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19462: MERGE on partitioned table with INSERT DEFAULT VALUES fails with "unknown action in MERGE WHEN clau
2026-05-17 20:21 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
BUG #19482: Recursive QueueFKConstraintValidation() lacks stack depth check
2026-05-16 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19482: Recursive QueueFKConstraintValidation() lacks stack depth check
2026-05-17 14:44 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[2+ messages in thread]
[PATCH] Replace debug-only Asserts with runtime checks in logical replication apply worker
2026-05-16 22:30 UTC Varik Matevosyan <varikmatevosyan@gmail.com>
` Re: [PATCH] Replace debug-only Asserts with runtime checks in logical replication apply worker
2026-05-17 01:40 UTC Noah Misch <noah@leadboat.com>
[2+ messages in thread]
BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-02 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-02 16:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-02 17:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-02 18:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-02 19:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-03 21:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-04 15:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-06 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-06 20:24 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2024-03-06 21:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault
2026-05-16 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
[11+ messages in thread]
Re: BUG #19354: JOHAB rejects valid byte sequences
2026-04-15 04:25 UTC Henson Choi <assam258@gmail.com>
` Re: BUG #19354: JOHAB rejects valid byte sequences
2026-04-15 05:57 UTC Henson Choi <assam258@gmail.com>
` Re: BUG #19354: JOHAB rejects valid byte sequences
2026-04-15 06:59 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19354: JOHAB rejects valid byte sequences
2026-05-14 19:36 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #19354: JOHAB rejects valid byte sequences
2026-05-16 09:39 UTC Henson Choi <assam258@gmail.com>
[5+ messages in thread]
BUG #19413: ASAN: stack-buffer-overflow in foldcase_options() with invalid ICU language tag
2026-02-19 05:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19413: ASAN: stack-buffer-overflow in foldcase_options() with invalid ICU language tag
2026-05-15 16:59 UTC Jeff Davis <pgsql@j-davis.com>
[2+ messages in thread]
BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-05-15 11:11 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19479: 04 is happening because your metadata is advertising a package version that is not actually present
2026-05-15 06:41 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19476: Segmentation fault in contrib/spi
2026-05-12 14:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-12 18:04 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-12 18:52 UTC pierre.forstmann@gmail.com
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-12 19:27 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-14 16:01 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-14 16:45 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-14 17:12 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19476: Segmentation fault in contrib/spi
2026-05-14 18:16 UTC Nathan Bossart <nathandbossart@gmail.com>
[8+ 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