pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19897: Recovery fails after "LOG: consistent recovery state reached"
2026-11-12 15:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"
2026-11-13 16:40 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"
2026-11-14 14:22 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"
2026-11-15 16:15 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"
2026-11-19 01:42 UTC TAKATSUKA Haruka <harukat@sraoss.co.jp>
[5+ messages in thread]
BUG #19915: Qual over function-wrapped grouping column pushed past DISTINCT ON returns wrong rows
2026-11-18 01:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19915: Qual over function-wrapped grouping column pushed past DISTINCT ON returns wrong rows
2026-11-18 21:29 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
BUG #19904: pg_column_is_updatable(): "negative bitmapset member not allowed" for large attnum (int16 overflow)
2026-11-15 04:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19904: pg_column_is_updatable(): "negative bitmapset member not allowed" for large attnum (int16 overflow)
2026-11-17 03:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19904: pg_column_is_updatable(): "negative bitmapset member not allowed" for large attnum (int16 overflow)
2026-11-18 20:10 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-09 06:49 UTC Giuliano Gagliardi <gogi@gogi.tv>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-11 19:48 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-11 19:56 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-12 00:34 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-12 15:47 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-13 02:08 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-02-13 23:37 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` 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 cca5507 <cca5507@qq.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-03-13 07:20 UTC cca5507 <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 cca5507 <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>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-07-16 09:19 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-07-21 18:55 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-07-27 20:28 UTC Robert Haas <robertmhaas@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-07-31 07:44 UTC Yugo Nagata <nagata@sraoss.co.jp>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-11-14 21:33 UTC Joao Rito <joaovictor.rito@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-11-17 05:36 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-11-17 21:37 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
2026-11-18 19:03 UTC João Rito <joaovictor.rito@gmail.com>
[26+ messages in thread]
Inconsistent time zone handling in timetz
2026-11-18 10:56 UTC miracee <sho@miracee.de>
` Re: Inconsistent time zone handling in timetz
2026-11-18 18:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Stale partition constraint on sub-partitions of a partitioned DEFAULT partition after a sibling is detached/dropped/created
2026-11-18 18:06 UTC Michael Ries <mries@salesforce.com>
ECPG: NULL pointer dereference in EXECUTE with a NULL parameter
2026-10-20 09:36 UTC Никита Лосев <nktlsv05@gmail.com>
` Re: ECPG: NULL pointer dereference in EXECUTE with a NULL parameter
2026-11-18 17:39 UTC Ishjaap Singh <ishjaap.singh07@gmail.com>
[2+ messages in thread]
BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-10-20 03:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-10-28 13:16 UTC Rajesh Kumar Thandapani <rajeshkumarth@google.com>
` Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-01 07:32 UTC Rajesh Kumar Thandapani <rajeshkumarth@google.com>
` Re: Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-03 11:01 UTC Raja Sai pranav <rajasaipranav0@gmail.com>
` Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-04 14:51 UTC Rajesh Kumar Thandapani <rajeshkumarth@google.com>
` Re: Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-07 15:21 UTC Raja Sai pranav <rajasaipranav0@gmail.com>
` Re: Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-16 05:12 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Re: Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-16 06:03 UTC Raja Sai pranav <rajasaipranav0@gmail.com>
` Re: Re: Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-16 13:36 UTC Rajesh Kumar Thandapani <rajeshkumarth@google.com>
` Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-17 04:17 UTC Raja Sai pranav <rajasaipranav0@gmail.com>
` Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-17 06:54 UTC Rajesh Kumar Thandapani <rajeshkumarth@google.com>
` Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
2026-11-18 13:05 UTC Raja Sai pranav <rajasaipranav0@gmail.com>
[12+ messages in thread]
BUG #19912: MERGE NOT MATCHED BY SOURCE sees stale source values after concurrent update (EPQ)
2026-11-17 14:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19912: MERGE NOT MATCHED BY SOURCE sees stale source values after concurrent update (EPQ)
2026-11-18 01:42 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19912: MERGE NOT MATCHED BY SOURCE sees stale source values after concurrent update (EPQ)
2026-11-18 12:30 UTC Tender Wang <tndrwang@gmail.com>
[3+ messages in thread]
Logical replication commits duplicates in DEFERRABLE unique indexes
2026-11-16 20:28 UTC Michael Malis <malis@pgrust.com>
` Re: Logical replication commits duplicates in DEFERRABLE unique indexes
2026-11-18 10:46 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
[2+ messages in thread]
BUG #19858: pg_dump --clean --if-exists fails on NOT VALID domain constraint
2026-11-09 13:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19858: pg_dump --clean --if-exists fails on NOT VALID domain constraint
2026-11-17 02:20 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19858: pg_dump --clean --if-exists fails on NOT VALID domain constraint
2026-11-18 09:57 UTC Dilip Kumar <dilipbalaut@gmail.com>
[3+ messages in thread]
BUG #19851: Adding a tautological CHECK(true) to a domain changes JSON_VALUE's result (silent NULL, value/type c
2026-11-08 03:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19851: Adding a tautological CHECK(true) to a domain changes JSON_VALUE's result (silent NULL, value/type c
2026-11-12 21:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19851: Adding a tautological CHECK(true) to a domain changes JSON_VALUE's result (silent NULL, value/type c
2026-11-13 13:28 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19851: Adding a tautological CHECK(true) to a domain changes JSON_VALUE's result (silent NULL, value/type c
2026-11-18 06:08 UTC Amit Langote <amitlangote09@gmail.com>
[4+ messages in thread]
BUG #19911: Window aggregate over ROWS n FOLLOWING: "unexpected end of tuplestore" after spill
2026-11-17 13:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19911: Window aggregate over ROWS n FOLLOWING: "unexpected end of tuplestore" after spill
2026-11-18 01:05 UTC Henson Choi <assam258@gmail.com>
` Re: BUG #19911: Window aggregate over ROWS n FOLLOWING: "unexpected end of tuplestore" after spill
2026-11-18 02:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19911: Window aggregate over ROWS n FOLLOWING: "unexpected end of tuplestore" after spill
2026-11-18 03:51 UTC Henson Choi <assam258@gmail.com>
[4+ messages in thread]
BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-15 18:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-16 18:56 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-16 19:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-16 20:23 UTC Борис Мурашов <murasovb@gmail.com>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-16 22:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-17 01:45 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-17 16:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-17 16:59 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
2026-11-18 02:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ 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>
` 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-06 09:21 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-06 09:33 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-07 10:08 UTC Zhijie Hou <houzhijie22@gmail.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-08 02:36 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-08 05:35 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-09 02:56 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-26 13:25 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-27 03:36 UTC Peter Smith <smithpb2250@gmail.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-27 06:42 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-28 08:41 UTC Chao Li <li.evan.chao@gmail.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-29 04:52 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-11-04 12:38 UTC Shlok Kyal <shlok.kyal.oss@gmail.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-11-04 13:24 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-11-05 10:43 UTC Shlok Kyal <shlok.kyal.oss@gmail.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-11-18 02:06 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[18+ messages in thread]
PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-16 11:26 UTC Tor Erik Linnerud <tel@jklm.no>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-16 16:29 UTC Andres Freund <andres@anarazel.de>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-16 20:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-16 22:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-17 10:03 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-17 14:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-17 23:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-17 23:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-17 23:49 UTC David Rowley <dgrowleyml@gmail.com>
` Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
2026-11-17 23:54 UTC David Rowley <dgrowleyml@gmail.com>
[10+ messages in thread]
BUG #19914: DETAIL: Could not open file 'pg_xact/0D7A': No such file or directory
2026-11-17 20:07 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19910: json(b)_to_tsvector() nested array filter gives internal error XX000 "unexpected end of flag array"
2026-11-17 05:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19910: json(b)_to_tsvector() nested array filter gives internal error XX000 "unexpected end of flag array"
2026-11-17 15:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19910: json(b)_to_tsvector() nested array filter gives internal error XX000 "unexpected end of flag array"
2026-11-17 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
[3+ messages in thread]
BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-11 22:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-13 11:32 UTC Nisha Moond <nisha.moond412@gmail.com>
` RE: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-16 08:01 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-16 12:19 UTC Nisha Moond <nisha.moond412@gmail.com>
` RE: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-16 13:08 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-16 15:15 UTC Nisha Moond <nisha.moond412@gmail.com>
` Re: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-16 15:46 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column
2026-11-17 15:32 UTC Nisha Moond <nisha.moond412@gmail.com>
[8+ messages in thread]
BUG #19913: Parent ALTER TABLE during concurrent DETACH leaves pending partition unusable (42804)
2026-11-17 15:01 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-02 22:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-04 16:14 UTC jian he <jian.universality@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-06 06:02 UTC Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-14 13:35 UTC Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-18 06:15 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-19 11:33 UTC Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-19 19:27 UTC Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-19 20:23 UTC Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-21 08:45 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-10-27 06:51 UTC Narayanan Venkateswaran <narayananvpostgres@gmail.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-11-13 04:33 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses
2026-11-17 12:03 UTC Nitin Motiani <nitinmotiani@google.com>
[12+ messages in thread]
Timing issue in pg_basebackup
2026-10-19 14:33 UTC Jesper St John <jesper@stjohn.se>
` Re: Timing issue in pg_basebackup
2026-10-20 21:11 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Timing issue in pg_basebackup
2026-10-21 17:16 UTC Jesper St John <jesper@stjohn.se>
` Re: Timing issue in pg_basebackup
2026-10-22 05:44 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Timing issue in pg_basebackup
2026-10-29 19:26 UTC Jesper St John <jesper@stjohn.se>
` Re: Timing issue in pg_basebackup
2026-11-09 13:19 UTC Jesper St John <jesper@stjohn.se>
` Re: Timing issue in pg_basebackup
2026-11-12 16:12 UTC Joao Rito <joaovictor.rito@gmail.com>
` Re: Timing issue in pg_basebackup
2026-11-12 21:19 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Timing issue in pg_basebackup
2026-11-16 10:26 UTC Magnus Hagander <magnus@hagander.net>
` Re: Timing issue in pg_basebackup
2026-11-16 12:08 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Timing issue in pg_basebackup
2026-11-17 11:35 UTC Jesper St John <admin@zonezero.se>
[11+ messages in thread]
BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
2026-11-12 23:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
2026-11-16 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
2026-11-16 19:10 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
2026-11-16 19:44 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
2026-11-17 00:55 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
2026-11-17 07:39 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[6+ messages in thread]
BUG #19909: BRIN redo: BufferIsPinned assert in brin_xlog_insert_update() if index was dropped or truncated
2026-11-17 05:03 UTC PG Bug reporting form <noreply@postgresql.org>
16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15
2026-11-16 20:51 UTC Adam Matthews <matthewsar@gmail.com>
` Re: 16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15
2026-11-16 22:39 UTC Andres Freund <andres@anarazel.de>
` Re: 16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15
2026-11-16 23:06 UTC Adam Matthews <matthewsar@gmail.com>
` Re: 16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15
2026-11-16 23:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: 16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15
2026-11-17 04:21 UTC Adam Matthews <matthewsar@gmail.com>
[5+ 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