pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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 <noreply@postgresql.org>
` 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 <maxim.boguk@gmail.com>
` 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 <maxim.boguk@gmail.com>
` 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 <andres@anarazel.de>
[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 <noreply@postgresql.org>
` Re: BUG #19527: Double-Abort Crash in `ResOwnerReleaseOSSLCipher` via `encrypt_iv` with Oversized Input
2026-06-22 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
2026-05-15 11:11 UTC PG Bug reporting form <noreply@postgresql.org>
` 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 <matheusssilv97@gmail.com>
` 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 <matheusssilv97@gmail.com>
` 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 <tgl@sss.pgh.pa.us>
` 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 <matheusssilv97@gmail.com>
` 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 <tgl@sss.pgh.pa.us>
` 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 <matheusssilv97@gmail.com>
` 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 <tgl@sss.pgh.pa.us>
` 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 <matheusssilv97@gmail.com>
` 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 <hlinnaka@iki.fi>
` 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 <nathandbossart@gmail.com>
` 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 <melanieplageman@gmail.com>
` 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 <tgl@sss.pgh.pa.us>
` 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 <tgl@sss.pgh.pa.us>
` 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 <matheusssilv97@gmail.com>
` 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 <tgl@sss.pgh.pa.us>
` 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 <matheusssilv97@gmail.com>
[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 <noreply@postgresql.org>
` Re: BUG #19530: Crash (SIGSEGV/SIGBUS) in parallel B-tree index vacuum during plain VACUUM
2026-06-22 09:51 UTC John Naylor <johncnaylorls@gmail.com>
[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 <noreply@postgresql.org>
` Re: BUG #19529: Documentation appears inconsistent with pg_dump --statistics behavior for CREATE STATISTICS objects
2026-06-20 15:55 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19529: Documentation appears inconsistent with pg_dump --statistics behavior for CREATE STATISTICS objects
2026-06-22 07:50 UTC Michael Paquier <michael@paquier.xyz>
[3+ messages in thread]
psql variable substitution in plpgsql loop
2026-06-21 17:38 UTC carl clemens <cclemens968@gmail.com>
` Re: psql variable substitution in plpgsql loop
2026-06-21 18:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: psql variable substitution in plpgsql loop
2026-06-21 19:27 UTC carl clemens <cclemens968@gmail.com>
[3+ messages in thread]
Rule on table with DO ALSO increments sequences twice
2026-06-21 10:06 UTC Tim Goddard <tim@goddard.nz>
BUG #19528: Assert failure in generate_normalized_query() via Squashed Array Literals
2026-06-19 04:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19528: Assert failure in generate_normalized_query() via Squashed Array Literals
2026-06-20 15:18 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19528: Assert failure in generate_normalized_query() via Squashed Array Literals
2026-06-20 16:30 UTC 王跃林 <violin0613@tju.edu.cn>
[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 <noreply@postgresql.org>
` Re:BUG #19501: btree_gist: use float4/float8 comparison functions to handle NaN correctly
2026-06-18 16:43 UTC =?utf-8?B?eWx3YW5ndGp1?= <ylwangtju@qq.com>
[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 <noreply@postgresql.org>
` 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 <ayushtiwari.slg01@gmail.com>
` 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 王跃林 <violin0613@tju.edu.cn>
` 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 <ayushtiwari.slg01@gmail.com>
` 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 王跃林 <violin0613@tju.edu.cn>
` 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 <ayushtiwari.slg01@gmail.com>
[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 <noreply@postgresql.org>
` 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 <pl0h0yp1@gmail.com>
` 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 <x4mmm@yandex-team.ru>
` 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 <hukutoc@gmail.com>
` 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 <x4mmm@yandex-team.ru>
` 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 <hukutoc@gmail.com>
` 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 <x4mmm@yandex-team.ru>
` 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 <amitlangote09@gmail.com>
` 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 <pl0h0yp1@gmail.com>
` 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 <hukutoc@gmail.com>
` 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 <amitlangote09@gmail.com>
` 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 <pl0h0yp1@gmail.com>
` 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 <amitlangote09@gmail.com>
[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 <noreply@postgresql.org>
` 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 <x4mmm@yandex-team.ru>
` 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 <michael@paquier.xyz>
` 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 <alvherre@kurilemu.de>
` 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 <x4mmm@yandex-team.ru>
` 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 Сергей Дм. Апойченко <sdaekb@yandex.ru>
` 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 <michael@paquier.xyz>
[7+ messages in thread]
[BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-02-19 13:43 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-02-23 08:26 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-02-25 16:32 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-02-25 16:57 UTC Álvaro Herrera <alvherre@kurilemu.de>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-02-26 03:16 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-02-26 06:04 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-03 07:33 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-08 21:14 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-09 04:52 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-09 09:39 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-27 04:33 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-03-27 05:54 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-06-10 13:04 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-06-16 18:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
` RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
2026-06-17 01:44 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[15+ 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 王跃林 <violin0613@tju.edu.cn>
` 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 <ayushtiwari.slg01@gmail.com>
` 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 <hlinnaka@iki.fi>
` 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 <ayushtiwari.slg01@gmail.com>
` 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 <hlinnaka@iki.fi>
[5+ messages in thread]
BUG #19518: Path resolution for loading a function fails, if postgres is somewhere in the path.
2026-06-12 19:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19518: Path resolution for loading a function fails, if postgres is somewhere in the path.
2026-06-13 00:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
[BUG] false positive in bt_index_check in case of short 4B varlena datum
2023-12-14 16:18 UTC Michael Zhilin <m.zhilin@postgrespro.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2023-12-14 17:17 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-07 18:04 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-07 18:33 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-07 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-08 14:34 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-09 17:59 UTC Michael Zhilin <m.zhilin@postgrespro.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-19 18:16 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-20 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-23 00:00 UTC jian he <jian.universality@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-23 18:09 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-23 19:24 UTC Michael Zhilin <m.zhilin@postgrespro.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-26 00:00 UTC jian he <jian.universality@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-01-26 07:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-03-20 10:24 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-03-20 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-03-20 17:00 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-03-21 05:46 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-03-23 00:39 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2024-03-23 11:37 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-01 17:11 UTC Andres Freund <andres@anarazel.de>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-01 18:06 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-01 19:41 UTC Andres Freund <andres@anarazel.de>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-03 18:17 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-03 19:44 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-04 05:20 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-08 23:07 UTC Michael Paquier <michael@paquier.xyz>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-12 09:17 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-05-12 10:22 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-06-11 07:57 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum
2026-06-12 01:32 UTC Michael Paquier <michael@paquier.xyz>
[31+ messages in thread]
[PATCH] contrib/xml2: backend crash in xpath_nodeset() on the namespace axis
2026-06-11 00:14 UTC Andrey Chernyy <andrey.cherny@tantorlabs.com>
` Re: [PATCH] contrib/xml2: backend crash in xpath_nodeset() on the namespace axis
2026-06-11 01:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: [PATCH] contrib/xml2: backend crash in xpath_nodeset() on the namespace axis
2026-06-11 22:59 UTC Andrey Chernyy <andrey.cherny@tantorlabs.com>
` Re: [PATCH] contrib/xml2: backend crash in xpath_nodeset() on the namespace axis
2026-06-12 01:27 UTC Michael Paquier <michael@paquier.xyz>
[4+ messages in thread]
BUG #19517: Eager Aggregation produces wrong count(*) when pushed into RHS of Hash Semi Join
2026-06-10 15:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19517: Eager Aggregation produces wrong count(*) when pushed into RHS of Hash Semi Join
2026-06-10 20:19 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19517: Eager Aggregation produces wrong count(*) when pushed into RHS of Hash Semi Join
2026-06-11 01:03 UTC Tender Wang <tndrwang@gmail.com>
[3+ messages in thread]
[PATCH] xml2: don't crash on namespace nodes in xpath_nodeset()
2026-06-10 23:24 UTC Andrey Chernyy <andrey.cherny@tantorlabs.com>
BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used.
2026-06-10 08:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used.
2026-06-10 14:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #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]
[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