pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-24 15:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-27 19:22 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-28 09:59 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-28 23:34 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-30 08:35 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-07-07 07:38 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-07-08 20:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[7+ messages in thread]
BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-06 13:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-06 17:01 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-08 18:25 UTC surya poondla <suryapoondla4@gmail.com>
[3+ messages in thread]
BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-03 13:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-05 08:20 UTC vaibhave postgres <postgresvaibhave@gmail.com>
` Re: BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-08 07:51 UTC Peter Eisentraut <peter@eisentraut.org>
[3+ messages in thread]
EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-02 16:58 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-02 22:10 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-03 03:06 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-03 08:36 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-06 02:17 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-07 13:49 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-07 14:20 UTC Thom Brown <thom@linux.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-08 00:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-08 00:42 UTC Thom Brown <thom@linux.com>
[9+ messages in thread]
BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-24 14:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-27 16:53 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-29 00:39 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-29 13:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 03:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 09:09 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 09:11 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 23:57 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-05 10:44 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-05 12:54 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-06 07:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-06 08:31 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 05:11 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 05:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 12:02 UTC David Rowley <dgrowleyml@gmail.com>
[15+ messages in thread]
BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-03 22:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:27 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:34 UTC Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:39 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 12:12 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-24 09:47 UTC Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-07-07 01:37 UTC Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-07-07 10:02 UTC Matheus Alcantara <matheusssilv97@gmail.com>
[8+ messages in thread]
BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2025-04-04 03:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-06-11 03:31 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-06-11 04:29 UTC TAKATSUKA Haruka <harukat@sraoss.co.jp>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-01 14:30 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-03 02:25 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-06 17:22 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-06 23:22 UTC Fujii Masao <masao.fujii@gmail.com>
[7+ messages in thread]
BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 07:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 14:41 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 18:19 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-07-05 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19543: ALTER RULE ... RENAME accepts reserved name "_RETURN" for a non-view rule; breaks a restored dump
2026-07-03 23:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19543: ALTER RULE ... RENAME accepts reserved name "_RETURN" for a non-view rule; breaks a restored dump
2026-07-04 14:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-16 11:29 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-17 19:19 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-18 05:24 UTC 王跃林 <violin0613@tju.edu.cn>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 14:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 15:43 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 17:46 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 23:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 08:40 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 13:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 16:48 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 17:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 19:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
Autoprewarm workers terminated due to a segmentation fault
2026-06-09 18:37 UTC Glauber Batista <glauberrbatista@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 21:06 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 21:44 UTC Tomas Vondra <tomas@vondra.me>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 22:25 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-11 14:40 UTC Tomas Vondra <tomas@vondra.me>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-15 14:35 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-26 17:55 UTC Tomas Vondra <tomas@vondra.me>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-26 18:07 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-29 15:12 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-07-01 19:16 UTC Glauber Batista <glauberrbatista@gmail.com>
[10+ messages in thread]
BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-28 02:14 UTC Bill Kim <billkimjh@gmail.com>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-28 18:54 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 12:04 UTC Bill Kim <billkimjh@gmail.com>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:27 UTC Bill Kim <billkimjh@gmail.com>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:50 UTC Bill Kim <billkimjh@gmail.com>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 23:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-07-01 13:38 UTC Bill Kim <billkimjh@gmail.com>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-07-01 17:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
BUG #19539: psql 17.6 on Windows 11 prints random garbage characters in Russian localized output of \d
2026-06-29 14:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19539: psql 17.6 on Windows 11 prints random garbage characters in Russian localized output of \d
2026-07-01 02:36 UTC Thomas Munro <thomas.munro@gmail.com>
[2+ messages in thread]
BUG #19540: Inconsistent integer-to-octal formatting for permission GUCs in pg_settings (boot_val vs setting)
2026-06-30 06:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19540: Inconsistent integer-to-octal formatting for permission GUCs in pg_settings (boot_val vs setting)
2026-06-30 15:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Set huge_page_size on 32bit system
2026-06-25 14:54 UTC Daria Shanina <vilensipkdm@gmail.com>
` Re: Set huge_page_size on 32bit system
2026-06-26 04:24 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Set huge_page_size on 32bit system
2026-06-26 05:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: Set huge_page_size on 32bit system
2026-06-26 08:13 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Set huge_page_size on 32bit system
2026-06-26 08:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: Set huge_page_size on 32bit system
2026-06-27 02:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: Set huge_page_size on 32bit system
2026-06-30 13:23 UTC Daria Shanina <vilensipkdm@gmail.com>
[7+ messages in thread]
BUG #17502: View based on window functions returns wrong results when queried
2022-05-28 22:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-29 14:21 UTC Magnus Hagander <magnus@hagander.net>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-29 18:58 UTC Daniel Farkaš <daniel.farkas@datoris.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-29 22:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 01:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 02:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 02:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 02:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 02:51 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 03:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 05:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 09:18 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2022-05-30 10:27 UTC Ilya Anfimov <ilan@tzirechnoy.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2023-01-30 22:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2023-01-31 07:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2023-01-31 11:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2026-06-29 23:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17502: View based on window functions returns wrong results when queried
2026-06-30 02:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[18+ messages in thread]
BUG #19535: Splitting window input targets can break same-level SRF lockstep semantics
2026-06-24 14:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19535: Splitting window input targets can break same-level SRF lockstep semantics
2026-06-29 23:32 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
BUG #19538: ALTER SYSTEM adds extra quotes
2026-06-29 08:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19538: ALTER SYSTEM adds extra quotes
2026-06-29 13:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
[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 <noreply@postgresql.org>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-28 11:33 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-28 13:43 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-29 01:22 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-29 01:41 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19534: Qual pushdown across a window subquery is unsafe with nondeterministic partition collations
2026-06-29 01:53 UTC Tender Wang <tndrwang@gmail.com>
[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 <noreply@postgresql.org>
` Re: BUG #19532: Window run-condition optimization can produce wrong results for count() window aggregates
2026-06-27 17:00 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
[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 <noreply@postgresql.org>
` 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 <david.g.johnston@gmail.com>
[2+ messages in thread]
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 <mbanck@gmx.net>
` 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 <x4mmm@yandex-team.ru>
` 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 <x4mmm@yandex-team.ru>
` 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 <emamuse86@gmail.com>
` 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 <sebas@mannem.nl>
[5+ messages in thread]
BUG #19531: Inconsistent Error Messages for the Same SQL Query
2026-06-24 07:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19531: Inconsistent Error Messages for the Same SQL Query
2026-06-24 08:19 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19531: Inconsistent Error Messages for the Same SQL Query
2026-06-24 08:20 UTC Francisco Olarte <folarte@peoplecall.com>
[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 wyuebei@gmail.com
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 <noreply@postgresql.org>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-15 09:14 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-15 23:24 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-17 04:15 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-17 08:19 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-17 20:26 UTC Sami Imseih <samimseih@gmail.com>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-18 01:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-18 03:22 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-18 05:40 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 07:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 11:09 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 12:15 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 16:45 UTC Lukas Fittl <lukas@fittl.com>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 16:58 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-20 22:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-22 08:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
2026-06-22 23:12 UTC Michael Paquier <michael@paquier.xyz>
[17+ 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