Mailing lists [pgsql-bugs]

1 July

• 06:25   Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure jian he
• 22:52   Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane

2 July

• 01:08   BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries PG Bug reporting form
• 02:10   BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server PG Bug reporting form
• 03:03   Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk
• 04:42   Re: BUG #16931: source code problem about commit_ts Andy Fan
• 09:32   Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
• 10:44   Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Sergei Kornilov
• 11:44   Re: BUG #16931: source code problem about commit_ts Fujii Masao
• 16:49   Re: BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server Laurenz Albe
• 22:21   Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Tom Lane

3 July

• 16:23   BUG #18977: Unexpected result of function to_char PG Bug reporting form
• 16:45   Re: BUG #18976: -0.0 with float8 will be transformed to 0 inpreparestatement but not in normal execution ZhangChi
• 17:40   Re: BUG #18977: Unexpected result of function to_char Laurenz Albe
• 17:42   Re: BUG #16931: source code problem about commit_ts Fujii Masao
• 18:06   Re: BUG #18977: Unexpected result of function to_char Tom Lane
• 19:13   BUG #18978: Index does not work in aggregate function filter PG Bug reporting form
• 19:36   Re: BUG #18978: Index does not work in aggregate function filter David G. Johnston

4 July

• 12:54   Unexpected behavior when setting "idle_replication_slot_timeout" Gunnar Morling
• 19:07   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 19:24   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao
• 21:59   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Gunnar Morling

5 July

• 01:08   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 07:22   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila
• 08:35   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 08:55   Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston
• 09:16   Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston
• 17:44   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao
• 17:53   Re: functional index search path issue. David G. Johnston
• 18:07   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao
• 18:10   Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston
• 18:12   Re: Unexpected behavior when setting "idle_replication_slot_timeout" David G. Johnston
• 19:13   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Tom Lane

6 July

• 18:11   Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 David G. Johnston
• 18:26   Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 Tom Lane
• 19:41   Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 David G. Johnston
• 20:53   Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1 Tom Lane

7 July

• 13:02   Re: BUG #18801: JIT recompiles function for each row if custom aggregation function is used Yura Sokolov
• 15:20   Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Sandeep Thakkar

8 July

• 00:47   Re: BUG #18980: Unable to perform make due to inability to resolve a variety of Undefined symbols arm64 Tom Lane
• 12:26   BUG #18981: Fault tolerance and improvement for xmltotext_with_options (xml.c) PG Bug reporting form
• 12:49   Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Robin Haberkorn
• 19:42   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao
• 19:51   Re: BUG #18981: Fault tolerance and improvement for xmltotext_with_options (xml.c) Tom Lane
• 19:53   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 20:48   Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions Jeff Davis

9 July

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

10 July

• 04:54   Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Thomas Munro
• 06:27   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Amit Kapila
• 07:35   PostgreSQL 18 beta1 - Segmentation fault on custom type casting Thomas Thai
• 08:27   RE: Unexpected behavior when setting "idle_replication_slot_timeout" Hayato Kuroda (Fujitsu)
• 08:51   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 10:03   Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Amit Kapila
• 10:15   Starting a PostgreSQL server on a dynamic port (parameter port=0) a.mitrokhin@postgrespro.ru
• 10:46   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Kirill Reshke
• 11:29   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) a.mitrokhin@postgrespro.ru
• 11:53   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Laurenz Albe
• 12:13   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Jim Jones
• 13:27   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao
• 13:59   Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting Aleksander Alekseev
• 14:58   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 16:21   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) David G. Johnston
• 17:12   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Euler Taveira
• 17:41   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) Tom Lane
• 17:55   Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting Tom Lane

11 July

• 01:36   Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Anthony Hsu
• 02:48   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Fujii Masao
• 05:32   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Laurenz Albe
• 09:57   Re: Unexpected behavior when setting "idle_replication_slot_timeout" Gunnar Morling
• 10:11   Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) a.mitrokhin@postgrespro.ru

13 July

• 13:52   Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English" Sandeep Thakkar

14 July

• 15:33   Re: BUG #18983: Problems with Postgres "make check" under ASAN Dmitry Kovalenko
• 16:41   Re: BUG #18983: Problems with Postgres "make check" under ASAN Aleksander Alekseev
• 22:00   BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti PG Bug reporting form
• 22:23   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 22:36   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane

15 July

• 00:11   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Aleksander Alekseev
• 00:33   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Aleksander Alekseev
• 00:40   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 01:05   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 02:17   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 06:54   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Michael Paquier
• 07:52   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Michael Paquier
• 07:59   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 13:23   BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate PG Bug reporting form
• 17:35   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate David G. Johnston
• 17:57   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik Dobák
• 17:57   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 17:59   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik Dobák
• 19:05   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 19:08   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Tom Lane
• 19:11   BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution PG Bug reporting form
• 19:22   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik Dobák
• 19:27   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate David G. Johnston
• 21:00   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Tom Lane
• 21:13   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Tom Lane
• 21:27   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Tom Lane
• 21:28   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate David G. Johnston
• 21:32   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik Dobák
• 21:38   Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate Erik Dobák

16 July

• 02:32   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Michael Paquier
• 02:40   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 03:10   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Michael Paquier
• 07:45   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Michael Paquier
• 12:33   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Yaroslav Syrytsia
• 12:55   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Dean Rasheed
• 13:42   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Dean Rasheed
• 13:48   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Michael Paquier
• 16:05   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Dean Rasheed
• 20:45   BUG #18987: psqlodbc_setup.exe installs as iso-8859-1 Publisher PG Bug reporting form
• 22:00   BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database PG Bug reporting form

17 July

• 01:54   Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting Thomas Thai
• 08:44   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Michael Paquier
• 09:46   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Dean Rasheed
• 12:25   Correct Behaviour for Concurrent partition detach Rohit Negi
• 12:58   Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Sajith Prabhakar Shetty
• 13:15   BUG #18989: Output of \sf does not match original source for E quoted strings (unlike \df+ used to) PG Bug reporting form
• 14:30   BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0) PG Bug reporting form
• 15:03   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Álvaro Herrera
• 15:06   Re: BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0) Dilip Kumar
• 16:09   Re: BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0) Dilip Kumar
• 16:20   Re: Correct Behaviour for Concurrent partition detach Álvaro Herrera
• 16:45   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 16:58   Re: BUG #18989: Output of \sf does not match original source for E quoted strings (unlike \df+ used to) Tom Lane
• 18:00   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane
• 18:05   Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan
• 18:48   Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Álvaro Herrera
• 18:49   Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Sajith Prabhakar Shetty
• 18:55   Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan

18 July

• 12:19   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Dean Rasheed
• 13:36   Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Yaroslav Syrytsia

19 July

• 12:43   BUG #18991: NUMA test fails on machine with two NUMA nodes when building 18beta2 PG Bug reporting form

20 July

• 17:31   BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe PG Bug reporting form

21 July

• 08:52   Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Dilip Kumar
• 10:21   Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Rahila Syed
• 15:29   BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary() PG Bug reporting form
• 17:29   Re: BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary() Nathan Bossart
• 17:38   Re: BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary() Tom Lane

22 July

• 05:27   Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Laurenz Albe
• 14:24   Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Shlok Kyal
• 15:21   RE: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Hayato Kuroda (Fujitsu)

23 July

• 02:23   [PERFORMANCE] regression: EXECUTE loop TRUNCATE slower in 17.5 vs 17.2 Guilherme Luis França
• 03:08   Re: [PERFORMANCE] regression: EXECUTE loop TRUNCATE slower in 17.5 vs 17.2 Tom Lane
• 04:39   Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Michael Paquier
• 06:50   Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Dilip Kumar
• 07:35   Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Shlok Kyal
• 12:19   Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Amit Kapila
• 12:24   Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load vignesh C
• 12:27   Re: Self referential foreign keys in partitioned table not working as expected Álvaro Herrera
• 13:00   BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message PG Bug reporting form
• 16:25   Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Shlok Kyal
• 17:27   Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane
• 17:44   Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane
• 18:31   Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Andrew Watkins
• 18:43   Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane
• 21:41   Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane
• 22:47   Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane