pgsql-bugs since 2025-06-22 00:00

If you find a bug, please use the bug reporting form.

Search the Archives

(enter a message-id to go directly to that message)
Advanced Search

Browse Archives

Prev | Next

June 22, 2025

Thread Author Time
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C 02:57
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin 12:00
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references πŸ“Ž Tom Lane 18:31

June 23, 2025

Thread Author Time
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila 02:52
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada 07:14
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo 09:13
RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu) 12:03
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada 14:05
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references πŸ“Ž Tom Lane 18:24

June 24, 2025

Thread Author Time
Re: BUG #18509: Logical decoding behaves badly when processing a change record for a table with altered column πŸ“Ž Ajin Cherian 00:20
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 πŸ“Ž Masahiko Sawada 01:24
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila 03:51
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Tom Lane 04:18
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada 04:22
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Tom Lane 04:34
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Michael Paquier 04:58
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 πŸ“Ž Masahiko Sawada 05:14
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin 07:00
BUG #18966: Invalid SQL queries hang indefinitely until server restart PG Bug reporting form 14:10
Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Tom Lane 19:09
BUG #18968: GiST Index Cost Estimation PG Bug reporting form 23:00

June 25, 2025

Thread Author Time
Re: BUG #16961: Could not access status of transaction Daniil Davydov 04:04
Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Laurenz Albe 05:36
BUG #18969: security tests failures PG Bug reporting form 06:15
Re: BUG #18969: security tests failures Daniel Gustafsson 12:31
Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart JΓ©rΓ©my Spriet 14:23
Re: PGXS does not properly uninstall documentation Karl O. Pinc 14:42
Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist πŸ“Ž Nathan Bossart 16:06

June 26, 2025

Thread Author Time
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane 18:37

June 27, 2025

Thread Author Time
Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar 05:05
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo 06:08
Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored πŸ“Ž Anthony Hsu 06:11
Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar 06:26
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo 06:29
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references πŸ“Ž Tom Lane 18:35
Re: BUG #18968: GiST Index Cost Estimation Tom Lane 21:03
Re: PGXS does not properly uninstall documentation Tom Lane 21:06
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane 21:37

June 28, 2025

Thread Author Time
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin 06:00
BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure PG Bug reporting form 07:00
BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program PG Bug reporting form 07:17
Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references πŸ“Ž Tom Lane 18:26
Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Tom Lane 19:13
Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Dmitry Kovalenko 19:32
Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Tom Lane 20:19
Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program David G. Johnston 21:12
Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored πŸ“Ž Anthony Hsu 23:37

June 29, 2025

Thread Author Time
Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Braulio Fdo Gonzalez 03:29
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure jian he 05:28
Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Laurenz Albe 06:00
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane 17:01
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure πŸ“Ž Tom Lane 17:32

June 30, 2025

Thread Author Time
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure jian he 01:47
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane 02:23
Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar 03:28
Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Masahiko Sawada 03:40
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure πŸ“Ž jian he 06:04
BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow PG Bug reporting form 13:44
Re: BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow Tom Lane 14:56
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane 15:14

July 1, 2025

Thread Author Time
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure πŸ“Ž jian he 03:25
Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier 06:49
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load πŸ“Ž Shlok Kyal 19:41
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane 19:52
BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries PG Bug reporting form 22:08
BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server PG Bug reporting form 23:10

July 2, 2025

Thread Author Time
Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk 00:03
Re: BUG #16931: source code problem about commit_ts πŸ“Ž Andy Fan 01:42
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada 06:32
Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk 06:35
Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk 07:04
Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Sergei Kornilov 07:44
Re: BUG #16931: source code problem about commit_ts Fujii Masao 08:44
Re: BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server Laurenz Albe 13:49
Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Tom Lane 19:21

July 3, 2025

Thread Author Time
BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution PG Bug reporting form 03:03
Re: BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution Laurenz Albe 12:23
Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution ZhangChi 12:30
BUG #18977: Unexpected result of function to_char PG Bug reporting form 13:23
Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution Laurenz Albe 13:27
Re: BUG #16931: source code problem about commit_ts Andy Fan 13:33
Re: BUG #18976: -0.0 with float8 will be transformed to 0 inpreparestatement but not in normal execution ZhangChi 13:45
Re: BUG #18977: Unexpected result of function to_char Laurenz Albe 14:40
Re: BUG #16931: source code problem about commit_ts Fujii Masao 14:42
Re: BUG #18977: Unexpected result of function to_char Tom Lane 15:06
Re: BUG #18977: Unexpected result of function to_char ZhangChi 15:49
BUG #18978: Index does not work in aggregate function filter PG Bug reporting form 16:13
Re: BUG #18978: Index does not work in aggregate function filter David G. Johnston 16:36
Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane 17:48

July 4, 2025

Thread Author Time
Unexpected behavior when setting "idle_replication_slot_timeout" Gunnar Morling 09:54
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Nisha Moond 12:14
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 14:12
Re: Unexpected behavior when setting "idle_replication_slot_timeout" πŸ“Ž Fujii Masao 15:22
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 16:07
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 16:24
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Gunnar Morling 18:59
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 22:08

July 5, 2025

Thread Author Time
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila 04:06
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila 04:22
Re: Unexpected behavior when setting "idle_replication_slot_timeout" πŸ“Ž Laurenz Albe 05:35
Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston 05:55
Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston 06:16
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 08:47
functional index search path issue. Kirill Reshke 11:45
Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston 14:38
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 14:44
Re: functional index search path issue. David G. Johnston 14:53
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 15:07
Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston 15:10
Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston 15:12
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Tom Lane 15:56
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Tom Lane 16:13

July 6, 2025

Thread Author Time
PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Ben Caspi 11:06
BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 PG Bug reporting form 13:58
Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 David G. Johnston 15:11
Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 Tom Lane 15:26
Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 David G. Johnston 16:41
Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 David G. Johnston 16:47
Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 Tom Lane 17:53

July 7, 2025

Thread Author Time
Re: BUG #18801: JIT recompiles function for each row if custom aggregation function is used Yura Sokolov 10:02
Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Sandeep Thakkar 12:20
BUG #18980: Unable to perform make due to inability to resolve a variety of Undefined symbols arm64 PG Bug reporting form 21:04
Re: BUG #18980: Unable to perform make due to inability to resolve a variety of Undefined symbols arm64 Tom Lane 21:47

July 8, 2025

Thread Author Time
BUG #18981: Fault tolerance and improvement for xmltotext_with_options (xml.c) PG Bug reporting form 09:26
Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Robin Haberkorn 09:49
Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier 11:23
Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Tom Lane 13:36
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 16:42
Re: BUG #18981: Fault tolerance and improvement for xmltotext_with_options (xml.c) Tom Lane 16:51
Re: Unexpected behavior when setting "idle_replication_slot_timeout" πŸ“Ž Laurenz Albe 16:53
Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions Jeff Davis 17:34
Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions Jeff Davis 17:48

July 9, 2025

Thread Author Time
Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier 00:45
Re: The same 2PC data maybe recovered twice suyu.cmj 01:57
Re: The same 2PC data maybe recovered twice suyu.cmj 05:51
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila 06:00
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila 06:35
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 07:12
RE: Unexpected behavior when setting "idle_replication_slot_timeout" πŸ“Ž Hayato Kuroda (Fujitsu) 07:24
Re: The same 2PC data maybe recovered twice Michael Paquier 07:35
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 09:21
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 10:19
Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Robin Haberkorn 11:28
Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Sandeep Thakkar 12:40
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 15:17
BUG #18983: Problems with Postgres "make check" under ASAN PG Bug reporting form 17:19
Re: BUG #18983: Problems with Postgres "make check" under ASAN Tom Lane 18:25

July 10, 2025

Thread Author Time
Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Thomas Munro 01:54
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila 03:27
PostgreSQL 18 beta1 - Segmentation fault on custom type casting Thomas Thai 04:35
RE: Unexpected behavior when setting "idle_replication_slot_timeout" Hayato Kuroda (Fujitsu) 05:27
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 05:51
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Amit Kapila 07:03
Starting a PostgreSQL server on a dynamic port (parameter port=0) a.mitrokhin 07:15
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Kirill Reshke 07:46
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) a.mitrokhin 08:29
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Laurenz Albe 08:53
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Jim Jones 09:13
Re: Unexpected behavior when setting "idle_replication_slot_timeout" πŸ“Ž Fujii Masao 10:27
Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting Aleksander Alekseev 10:59
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 11:58
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) David G. Johnston 13:21
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Euler Taveira 14:12
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Tom Lane 14:41
Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting Tom Lane 14:55
Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Anthony Hsu 22:36
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao 23:48

July 11, 2025

Thread Author Time
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe 02:32
Re: Unexpected behavior when setting "idle_replication_slot_timeout" Gunnar Morling 06:57
Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) a.mitrokhin 07:11

July 13, 2025

Thread Author Time
Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Sandeep Thakkar 10:52

July 14, 2025

Thread Author Time
Re: The same 2PC data maybe recovered twice πŸ“Ž 06:46
Re: The same 2PC data maybe recovered twice Michael Paquier 08:14
Re: The same 2PC data maybe recovered twice suyu.cmj 09:57
Re: BUG #18983: Problems with Postgres "make check" under ASAN Dmitry Kovalenko 12:33
Re: BUG #18983: Problems with Postgres "make check" under ASAN Aleksander Alekseev 13:41
BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti PG Bug reporting form 19:00
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane 19:23
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane 19:36
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti πŸ“Ž Aleksander Alekseev 21:11
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Aleksander Alekseev 21:33
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti πŸ“Ž Tom Lane 21:40
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti πŸ“Ž Tom Lane 22:05
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane 23:17

July 15, 2025

Thread Author Time
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Michael Paquier 03:54
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Michael Paquier 04:52
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane 04:59
BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate PG Bug reporting form 10:23
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti πŸ“Ž Álvaro Herrera 12:33
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate David G. Johnston 14:35
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik DobΓ‘k 14:57
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane 14:57
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik DobΓ‘k 14:59
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane 16:05
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Tom Lane 16:08
BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution PG Bug reporting form 16:11
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik DobΓ‘k 16:22
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate David G. Johnston 16:27
Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Tom Lane 18:00
Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Tom Lane 18:13

Browse Archives

Prev | Next