pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-22 08:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-23 07:49 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-28 06:48 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-29 10:56 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2025-12-30 06:55 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2026-01-08 22:46 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2026-01-09 04:46 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2026-01-10 00:56 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2026-04-03 07:24 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2026-04-07 08:13 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
2026-06-04 11:37 UTC Ajin Cherian <itsajin@gmail.com>
[11+ messages in thread]
BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-05-26 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-05-28 03:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-05-28 05:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-05-29 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-05-29 05:00 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-05-31 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-06-01 02:11 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-06-01 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-06-01 06:18 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
2026-06-02 23:59 UTC Michael Paquier <michael@paquier.xyz>
[10+ messages in thread]
BUG #19504: Segmentation fault in plpython3u function (pg19)
2026-06-02 08:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19504: Segmentation fault in plpython3u function (pg19)
2026-06-02 19:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
GREATEST/LEAST ignores comparison operator volatility in contain_volatile_functions_walker
2026-06-02 08:48 UTC Mats Rydberg <mats@planetscale.com>
` Re: GREATEST/LEAST ignores comparison operator volatility in contain_volatile_functions_walker
2026-06-02 19:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
R: 14.1 immutable function, bad performance if check number = 'NaN'
2022-04-26 07:45 UTC Federico Travaglini <federico.travaglini@collaboration.aubay.it>
` Re: R: 14.1 immutable function, bad performance if check number = 'NaN'
2022-04-26 14:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` [PATCH] Have RepackDecodingState carry a magic number
2026-06-01 16:43 UTC Álvaro Herrera <alvherre@kurilemu.de>
` [PATCH] Have RepackDecodingState carry a magic number
2026-06-01 16:43 UTC Álvaro Herrera <alvherre@kurilemu.de>
[4+ messages in thread]
BUG #19502: unix_socket_group doesn't work anymore
2026-05-31 14:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19502: unix_socket_group doesn't work anymore
2026-05-31 16:47 UTC Pierre Juhen <pierre.juhen@orange.fr>
[2+ messages in thread]
BUG #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>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-26 08:02 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-26 08:30 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-26 08:41 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-26 09:27 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-26 09:33 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-26 12:28 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-26 18:29 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-27 00:30 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-27 02:55 UTC Nazneen Jafri <jafrinazneen@gmail.com>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-27 09:06 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-27 12:08 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-28 01:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
2026-05-29 18:06 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-31 10:14 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[22+ messages in thread]
BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-26 14:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-26 17:52 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 00:49 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 00:59 UTC Калинин Никита <n.kalinin@postgrespro.ru>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 01:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 01:17 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 01:28 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 03:50 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-27 07:16 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-29 02:03 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
2026-05-29 18:02 UTC Robert Haas <robertmhaas@gmail.com>
[11+ messages in thread]
BUG #19499: Extensions Powa and Powa-archivist are missing in official download repository
2026-05-28 05:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19499: Extensions Powa and Powa-archivist are missing in official download repository
2026-05-28 13:44 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
BUG #19496: Assert("ItemPointerIsValid(pointer)") when using pageinspect
2026-05-27 05:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19496: Assert("ItemPointerIsValid(pointer)") when using pageinspect
2026-05-27 13:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
16.14 regression: startup process self-deadlocks during multixact WAL replay in RecordNewMultiXact
2026-05-27 12:33 UTC Olegs Germanovs <olegs.germanovs@gmail.com>
` Re: 16.14 regression: startup process self-deadlocks during multixact WAL replay in RecordNewMultiXact
2026-05-27 12:48 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[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>
` Re: BUG #19482: Recursive QueueFKConstraintValidation() lacks stack depth check
2026-05-26 15:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #19492: intarray: fix variable stats leak in _int_matchsel
2026-05-24 05:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #19492: intarray: fix variable stats leak in _int_matchsel
2026-05-24 05:15 UTC =?gb18030?B?emVuZ21hbg==?= <zengman@halodbtech.com>
` Re: BUG #19492: intarray: fix variable stats leak in _int_matchsel
2026-05-25 22:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ 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>
` Re: BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT
2026-05-25 21:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-16 15:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-17 12:14 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-03-17 12:26 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-17 12:33 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-17 12:59 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-17 13: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-03-17 13:24 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-17 13:30 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-17 17:46 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 01:12 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 05:44 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 05:56 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-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>
` Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
2026-05-25 19:26 UTC Alexander Korotkov <aekorotkov@gmail.com>
[34+ 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]
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 #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 11:57 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 13:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 13:45 UTC Andres Freund <andres@anarazel.de>
` 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: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 15:56 UTC Long76 <long76.git@mail.ru>
` Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-02-05 10:05 UTC Nitin Motiani <nitinmotiani@google.com>
` 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>
[7+ 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]
[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]
[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