public inbox for [email protected]
help / color / mirror / Atom feedBUG #19538: ALTER SYSTEM adds extra quotes
2026-06-29 08:08 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19538: ALTER SYSTEM adds extra quotes
2026-06-29 13:55 UTC Tom Lane <[email protected]>
[2+ messages in thread]
BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-24 14:45 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-28 11:33 UTC Tender Wang <[email protected]>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-28 13:43 UTC Chengpeng Yan <[email protected]>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-29 01:22 UTC Tender Wang <[email protected]>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-29 01:41 UTC Richard Guo <[email protected]>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-29 01:53 UTC Tender Wang <[email protected]>
[6+ messages in thread]
BUG #19532: Window run-condition optimization can produce wrong results for count() window aggregates
2026-06-24 14:34 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19532: Window run-condition optimization can produce wrong results for count() window aggregates
2026-06-27 17:00 UTC Chengpeng Yan <[email protected]>
[2+ messages in thread]
BUG #19537: Authentication failed regardless of typing exactly my password set from sudo passwd postgres
2026-06-26 15:56 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19537: Authentication failed regardless of typing exactly my password set from sudo passwd postgres
2026-06-27 15:32 UTC David G. Johnston <[email protected]>
[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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` 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 <[email protected]>
` Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8)
2026-06-25 09:30 UTC Michael Banck <[email protected]>
` Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8)
2026-06-25 10:14 UTC Andrey Borodin <[email protected]>
` Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8)
2026-06-25 10:17 UTC Andrey Borodin <[email protected]>
` Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8)
2026-06-25 13:14 UTC Emanuele <[email protected]>
` Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8)
2026-06-25 13:43 UTC Sebastiaan Mannem <[email protected]>
[27+ messages in thread]
BUG #19484: Segmentation fault triggered by FDW
2026-05-18 06:38 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-05-20 12:37 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-05-20 17:46 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-05-22 20:56 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-05-30 06:18 UTC Rafia Sabih <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-09 15:10 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-10 05:15 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-10 11:08 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-10 13:09 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-10 13:27 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-11 10:40 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-11 10:44 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-18 09:15 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-18 10:50 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-18 10:55 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-18 10:57 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-19 11:59 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-22 08:28 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-23 08:27 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 00:00 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 01:43 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 01:53 UTC Tom Lane <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 02:23 UTC Richard Guo <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 03:50 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 04:25 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 09:15 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 11:20 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 17:02 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-24 23:24 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-25 06:15 UTC Etsuro Fujita <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-25 11:47 UTC Amit Langote <[email protected]>
` Re: BUG #19484: Segmentation fault triggered by FDW
2026-06-25 12:21 UTC Amit Langote <[email protected]>
[32+ messages in thread]
Two bugs around ALTER TYPE
2026-04-14 11:53 UTC Andrey Borodin <[email protected]>
` Re: Two bugs around ALTER TYPE
2026-06-24 23:56 UTC surya poondla <[email protected]>
[2+ messages in thread]
BUG #19531: Inconsistent Error Messages for the Same SQL Query
2026-06-24 07:20 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19531: Inconsistent Error Messages for the Same SQL Query
2026-06-24 08:19 UTC Laurenz Albe <[email protected]>
` Re: BUG #19531: Inconsistent Error Messages for the Same SQL Query
2026-06-24 08:20 UTC Francisco Olarte <[email protected]>
[3+ messages in thread]
pg ctl start spawns visible cmd.exe console window on Windows — CreateProcessAsUser missing CREATE NO WINDOW
2026-06-24 06:15 UTC [email protected]
BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-14 16:05 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-15 09:14 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-15 23:24 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-17 04:15 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-17 08:19 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-17 20:26 UTC Sami Imseih <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-18 01:03 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-18 03:22 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-18 05:40 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 07:43 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 11:09 UTC Álvaro Herrera <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 12:15 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 16:45 UTC Lukas Fittl <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 16:58 UTC Álvaro Herrera <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 22:51 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-22 08:28 UTC Michael Paquier <[email protected]>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-22 23:12 UTC Michael Paquier <[email protected]>
[17+ messages in thread]
BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
2026-06-02 18:36 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
2026-06-02 18:51 UTC Maxim Boguk <[email protected]>
` Re: BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
2026-06-22 20:22 UTC Maxim Boguk <[email protected]>
` Re: BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
2026-06-22 20:53 UTC Andres Freund <[email protected]>
[4+ messages in thread]
BUG #19527: Double-Abort Crash in `ResOwnerReleaseOSSLCipher` via `encrypt_iv` with Oversized Input
2026-06-18 18:17 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19527: Double-Abort Crash in `ResOwnerReleaseOSSLCipher` via `encrypt_iv` with Oversized Input
2026-06-22 16:37 UTC Tom Lane <[email protected]>
[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 <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-05-25 22:26 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-05-28 14:10 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-05-28 15:12 UTC Tom Lane <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-01 22:14 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-01 23:26 UTC Tom Lane <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-05 18:09 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-05 19:11 UTC Tom Lane <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-05 19:35 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-17 15:30 UTC Heikki Linnakangas <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-17 15:43 UTC Nathan Bossart <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-17 15:43 UTC Melanie Plageman <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-17 15:56 UTC Tom Lane <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-17 21:56 UTC Tom Lane <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-18 12:13 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-21 19:40 UTC Tom Lane <[email protected]>
` Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-06-22 10:18 UTC Matheus Alcantara <[email protected]>
[17+ messages in thread]
BUG #19530: Crash (SIGSEGV/SIGBUS) in parallel B-tree index vacuum during plain VACUUM
2026-06-21 21:38 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19530: Crash (SIGSEGV/SIGBUS) in parallel B-tree index vacuum during plain VACUUM
2026-06-22 09:51 UTC John Naylor <[email protected]>
[2+ messages in thread]
BUG #19529: Documentation appears inconsistent with pg_dump --statistics behavior for CREATE STATISTICS objects
2026-06-19 07:17 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19529: Documentation appears inconsistent with pg_dump --statistics behavior for CREATE STATISTICS objects
2026-06-20 15:55 UTC Fujii Masao <[email protected]>
` Re: BUG #19529: Documentation appears inconsistent with pg_dump --statistics behavior for CREATE STATISTICS objects
2026-06-22 07:50 UTC Michael Paquier <[email protected]>
[3+ messages in thread]
psql variable substitution in plpgsql loop
2026-06-21 17:38 UTC carl clemens <[email protected]>
` Re: psql variable substitution in plpgsql loop
2026-06-21 18:17 UTC David G. Johnston <[email protected]>
` Re: psql variable substitution in plpgsql loop
2026-06-21 19:27 UTC carl clemens <[email protected]>
[3+ messages in thread]
Rule on table with DO ALSO increments sequences twice
2026-06-21 10:06 UTC Tim Goddard <[email protected]>
BUG #19528: Assert failure in generate_normalized_query() via Squashed Array Literals
2026-06-19 04:40 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19528: Assert failure in generate_normalized_query() via Squashed Array Literals
2026-06-20 15:18 UTC Fujii Masao <[email protected]>
` Re: BUG #19528: Assert failure in generate_normalized_query() via Squashed Array Literals
2026-06-20 16:30 UTC 王跃林 <[email protected]>
[3+ messages in thread]
BUG #19501: btree_gist: use float4/float8 comparison functions to handle NaN correctly
2026-05-29 15:35 UTC PG Bug reporting form <[email protected]>
` Re:BUG #19501: btree_gist: use float4/float8 comparison functions to handle NaN correctly
2026-06-18 16:43 UTC =?utf-8?B?eWx3YW5ndGp1?= <[email protected]>
[2+ messages in thread]
BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator
2026-06-18 07:52 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator
2026-06-18 13:36 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator
2026-06-18 13:43 UTC 王跃林 <[email protected]>
` Re: BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator
2026-06-18 13:48 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator
2026-06-18 14:02 UTC 王跃林 <[email protected]>
` Re: BUG #19524: In `contrib/btree_gist` float4/float8 GiST index operations, handling NaN values with raw C operator
2026-06-18 14:23 UTC Ayush Tiwari <[email protected]>
[6+ messages in thread]
BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-04-17 11:20 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-04-20 13:38 UTC Andrey Rachitskiy <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-04-23 18:55 UTC Andrey Borodin <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-04-28 20:19 UTC Nikita Malakhov <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-04-30 12:03 UTC Andrey Borodin <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-05-26 11:17 UTC Nikita Malakhov <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-05-31 13:33 UTC Andrey Borodin <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-06-05 08:58 UTC Amit Langote <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-06-05 10:03 UTC Andrey Rachitskiy <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-06-05 10:57 UTC Nikita Malakhov <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-06-17 08:27 UTC Amit Langote <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-06-17 09:57 UTC Andrey Rachitskiy <[email protected]>
` Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables
2026-06-18 06:57 UTC Amit Langote <[email protected]>
[13+ messages in thread]
BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 13:39 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-15 17:44 UTC Andrey Borodin <[email protected]>
` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-16 03:46 UTC Michael Paquier <[email protected]>
` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-16 18:36 UTC Álvaro Herrera <[email protected]>
` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-16 18:43 UTC Andrey Borodin <[email protected]>
` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-17 16:49 UTC Сергей Дм. Апойченко <[email protected]>
` Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
2026-06-17 23:27 UTC Michael Paquier <[email protected]>
[7+ messages in thread]
Possible G2-item at SERIALIZABLE
2026-05-22 16:44 UTC Kyle Kingsbury <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-05-30 18:47 UTC Andrey Borodin <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-05-31 13:19 UTC Andrey Borodin <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 01:49 UTC Kyle Kingsbury <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 06:18 UTC Andrey Borodin <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 10:11 UTC Andrey Borodin <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 22:00 UTC Zsolt Parragi <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-02 08:18 UTC Andrey Borodin <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-02 23:03 UTC Zsolt Parragi <[email protected]>
` Re: Possible G2-item at SERIALIZABLE
2026-06-17 17:39 UTC Andrey Borodin <[email protected]>
[10+ messages in thread]
RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-27 04:33 UTC Hayato Kuroda (Fujitsu) <[email protected]>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-27 05:54 UTC Vishal Prasanna <[email protected]>
` Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-06-10 13:04 UTC Álvaro Herrera <[email protected]>
` Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-06-16 18:22 UTC Álvaro Herrera <[email protected]>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-06-17 01:44 UTC Hayato Kuroda (Fujitsu) <[email protected]>
[5+ messages in thread]
Fw:Re: Fw: ltree_compare in contrib/ltree/ltree_op.c overflows int32 on deep ltree comparisons, returning the wrong sign
2026-06-13 03:50 UTC 王跃林 <[email protected]>
` Re: Fw:Re: Fw: ltree_compare in contrib/ltree/ltree_op.c overflows int32 on deep ltree comparisons, returning the wrong sign
2026-06-13 06:12 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: ltree_compare in contrib/ltree/ltree_op.c overflows int32 on deep ltree comparisons, returning the wrong sign
2026-06-15 15:08 UTC Heikki Linnakangas <[email protected]>
` Re: Fw:Re: Fw: ltree_compare in contrib/ltree/ltree_op.c overflows int32 on deep ltree comparisons, returning the wrong sign
2026-06-15 15:24 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: ltree_compare in contrib/ltree/ltree_op.c overflows int32 on deep ltree comparisons, returning the wrong sign
2026-06-16 06:37 UTC Heikki Linnakangas <[email protected]>
[5+ 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