agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19516: Mixup of OLD/NEW with RETURNING when parenthesized
2026-06-10 10:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19516: Mixup of OLD/NEW with RETURNING when parenthesized
2026-06-10 10:50 UTC Marko Grujic <markoog@gmail.com>
[2+ messages in thread]
BUG #19470: PostgreSQL backend aborts (assert failure) when a prepared statement returns a composite type cast t
2026-04-29 11:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19470: PostgreSQL backend aborts (assert failure) when a prepared statement returns a composite type cast t
2026-05-03 19:11 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19470: PostgreSQL backend aborts (assert failure) when a prepared statement returns a composite type cast t
2026-05-05 02:36 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #19470: PostgreSQL backend aborts (assert failure) when a prepared statement returns a composite type cast t
2026-06-10 09:40 UTC Amit Langote <amitlangote09@gmail.com>
[4+ messages in thread]
BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-04 14:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-05 03:18 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-05 03:42 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-05 07:58 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-05 08:47 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-05 15:29 UTC Ashutosh Sharma <ashu.coek88@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-05 15:38 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-08 23:44 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-09 04:38 UTC Ashutosh Sharma <ashu.coek88@gmail.com>
` Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
2026-06-10 03:34 UTC Fujii Masao <masao.fujii@gmail.com>
[10+ messages in thread]
BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-05-28 14:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-05-29 14:23 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-01 17:12 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-02 02:39 UTC Никита Калинин <n.kalinin@postgrespro.ru>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-02 12:25 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-03 05:51 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-03 07:30 UTC Antonin Houska <ah@cybertec.at>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-03 10:25 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-03 21:02 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-04 06:31 UTC Antonin Houska <ah@cybertec.at>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-05 06:09 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` RE: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-05 08:08 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-08 19:50 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
2026-06-09 18:18 UTC Alvaro Herrera <alvherre@kurilemu.de>
[14+ messages in thread]
[PATCH v2] Disallow direct use of the pgrepack plugin
2026-06-08 18:57 UTC Álvaro Herrera <alvherre@kurilemu.de>
` [PATCH v2] Disallow direct use of the pgrepack plugin
2026-06-08 18:57 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
Hashed SAOP on composite type with non-hashable column errors at runtime
2026-06-05 14:27 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Hashed SAOP on composite type with non-hashable column errors at runtime
2026-06-05 18:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Hashed SAOP on composite type with non-hashable column errors at runtime
2026-06-05 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Hashed SAOP on composite type with non-hashable column errors at runtime
2026-06-07 17:56 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Hashed SAOP on composite type with non-hashable column errors at runtime
2026-06-08 16:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Logical replication initialization time depends dramatically on the publication "schema" size
2026-06-05 10:11 UTC Crimean (gmail) <crimean.celica@gmail.com>
` RE: Logical replication initialization time depends dramatically on the publication "schema" size
2026-06-08 12:31 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[2+ messages in thread]
BUG #19514: pg_hba error when configuring SSL Replication
2026-06-08 11:59 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2023-10-16 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-05-12 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-05-13 00:46 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-05-13 06:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-05-14 07:19 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-05 02:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-05 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-05 05:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-06 00:13 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-06 12:45 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-08 05:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
2026-06-08 08:43 UTC Xuneng Zhou <xunengzhou@gmail.com>
[12+ messages in thread]
BUG #19513: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-07 06:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19513: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-07 20:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-03 16:22 UTC violin0613@tju.edu.cn <violin0613@tju.edu.cn>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-03 22:31 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-04 02:47 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-04 07:31 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-04 09:12 UTC Ashutosh Sharma <ashu.coek88@gmail.com>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-04 23:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-05 06:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-05 08:00 UTC Ashutosh Sharma <ashu.coek88@gmail.com>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-06 00:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fw: Re: heap_force_common in contrib/pg_surgery/heap_surgery.c has an off by one stack buffer overflow
2026-06-06 01:08 UTC surya poondla <suryapoondla4@gmail.com>
[10+ messages in thread]
BUG #19511: contrib/dblink: NULL dereference in dblink_get_notify() when called without a prior connection
2026-06-05 01:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19511: contrib/dblink: NULL dereference in dblink_get_notify() when called without a prior connection
2026-06-05 01:19 UTC Amjad Shahzad <amjadshahzad2000@gmail.com>
` Re: BUG #19511: contrib/dblink: NULL dereference in dblink_get_notify() when called without a prior connection
2026-06-05 04:45 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19511: contrib/dblink: NULL dereference in dblink_get_notify() when called without a prior connection
2026-06-05 10:55 UTC Amjad Shahzad <amjadshahzad2000@gmail.com>
` Re: BUG #19511: contrib/dblink: NULL dereference in dblink_get_notify() when called without a prior connection
2026-06-05 15:15 UTC Fujii Masao <masao.fujii@gmail.com>
[5+ messages in thread]
BUG #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and hash_bytes (HashAgg executor)
2026-06-05 01:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and hash_bytes (HashAgg executor)
2026-06-05 14:10 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
Re: BUG #19510: refint.c: SQL injection via unquoted identifier arguments in check_primary_key and check_foreign_key
2026-06-04 23:50 UTC Amjad Shahzad <amjadshahzad2000@gmail.com>
` Re: BUG #19510: refint.c: SQL injection via unquoted identifier arguments in check_primary_key and check_foreign_key
2026-06-05 00:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19510: refint.c: SQL injection via unquoted identifier arguments in check_primary_key and check_foreign_key
2026-06-05 00:29 UTC Amjad Shahzad <amjadshahzad2000@gmail.com>
[3+ messages in thread]
BUG #19509: Typo in 19 beta release notes (debug_print_parse)
2026-06-04 14:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19509: Typo in 19 beta release notes (debug_print_parse)
2026-06-04 15:22 UTC Sergey Shinderuk <s.shinderuk@postgrespro.ru>
` Re: BUG #19509: Typo in 19 beta release notes (debug_print_parse)
2026-06-04 15:35 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #19509: Typo in 19 beta release notes (debug_print_parse)
2026-06-04 16:24 UTC Bruce Momjian <bruce@momjian.us>
[4+ messages in thread]
Warning while compiling 19beta1
2026-06-04 14:35 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Warning while compiling 19beta1
2026-06-04 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Warning while compiling 19beta1
2026-06-04 15:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Warning while compiling 19beta1
2026-06-04 15:12 UTC hubert depesz lubaczewski <depesz@depesz.com>
[4+ messages in thread]
BUG #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]
[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