Mailing lists [pgsql-bugs]

1 December

• 20:25   Re: encrypted pk8 keys work with libpg connection but not in postgres_fdw Dave Cramer

2 December

• 13:07   BUG #18729: update with multiple subpartitions return error: too many range table entries PG Bug reporting form
• 14:36   Re: BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks Bertrand Drouvot
• 21:37   Re: BUG #18729: update with multiple subpartitions return error: too many range table entries Euler Taveira

3 December

• 05:00   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
• 05:16   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 05:37   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bruce Momjian
• 07:31   BUG #18730: Inequality comparison operators and SMALLINT negative immediate value PG Bug reporting form
• 07:41   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 12:03   Re: BUG #18707: Installation issue Sandeep Thakkar
• 13:38   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
• 14:03   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Thomas Munro
• 15:49   BUG #18731: The psql \d command does not exactly match but can be executed PG Bug reporting form
• 18:23   BUG #18732: Segfault in pgbench on max_connections starvation PG Bug reporting form
• 18:36   AW: BUG #18725: "set role" requires "grant connect on database" PostgreSQL TDBA (LDBV)
• 19:48   Re: BUG #18730: Inequality comparison operators and SMALLINT negative immediate value David G. Johnston
• 20:52   Re: BUG #18732: Segfault in pgbench on max_connections starvation Heikki Linnakangas
• 21:27   Re: BUG #18732: Segfault in pgbench on max_connections starvation Andres Freund
• 21:42   BUG #18733: Connection Timeout after upgrade PG Bug reporting form
• 23:02   Re: BUG #18731: The psql \d command does not exactly match but can be executed Tom Lane

4 December

• 08:50   Re: BUG #18731: The psql \d command does not exactly match but can be executed zengman
• 15:42   Issue with pg_dump Including Ownership Metadata for pg_trgm Extension in PostgreSQL 17 AKASH
• 22:37   Re: Issue with pg_dump Including Ownership Metadata for pg_trgm Extension in PostgreSQL 17 Tom Lane

5 December

• 05:55   BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active" PG Bug reporting form
• 07:04   Tablespace storage bug... Greg Kemnitz
• 07:09   Re: Tablespace storage bug... David G. Johnston
• 08:12   Re: Tablespace storage bug... Greg Kemnitz
• 08:25   BUG #18735: Specific multibyte character in psql file path command parameter for Windows PG Bug reporting form

6 December

• 00:07   Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active" Tom Lane
• 00:50   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 02:13   Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active" Andres Freund
• 10:12   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Koichi Suzuki
• 11:05   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 11:21   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tatsuo Ishii
• 11:26   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Koichi Suzuki
• 11:44   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 11:54   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 12:11   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Koichi Suzuki
• 12:13   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Koichi Suzuki
• 12:29   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tatsuo Ishii
• 12:42   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tatsuo Ishii
• 18:44   FF3 vs MS Date/Time Template - ERROR: date/time field value out of range Nick Davies
• 19:21   Re: Install postgres 14 on SLES 15 SP1 Laurenz Albe
• 23:15   Re: Dangling operator family after DROP TYPE Tom Lane

7 December

• 00:36   Re: Dangling operator family after DROP TYPE Peter Geoghegan
• 00:44   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 02:14   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 04:51   Re: Dangling operator family after DROP TYPE Tom Lane
• 05:14   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tatsuo Ishii
• 06:07   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 17:42   Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan
• 23:49   Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range Tom Lane

8 December

• 16:37   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tatsuo Ishii
• 17:01   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tatsuo Ishii
• 18:00   BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error PG Bug reporting form

9 December

• 04:55   Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows Tom Lane
• 08:56   Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error Tender Wang
• 15:16   Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range Nick Davies
• 17:23   BUG #18742: /src/backend/rewrite/rewriteHandler.c PG Bug reporting form
• 17:26   BUG #18743: /src/backend/rewrite/rewriteHandler.c PG Bug reporting form
• 17:27   BUG #18744: /src/bin/pg_dump/pg_backup_archiver.c PG Bug reporting form
• 19:07   BUG #18745: /src/bin/pg_waldump/compat.c PG Bug reporting form
• 19:08   BUG #18746: /src/backend/parser/parse_utilcmd.c PG Bug reporting form
• 20:27   Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity Tomas Vondra
• 20:33   Re: BUG #18746: /src/backend/parser/parse_utilcmd.c Alvaro Herrera
• 21:50   Re: BUG #18742: /src/backend/rewrite/rewriteHandler.c Tom Lane

10 December

• 00:37   Re: BUG #18743: /src/backend/rewrite/rewriteHandler.c David Rowley
• 02:00   Re: BUG #18585: Date/time conversion functions are not protected against integer overflow Nathan Bossart
• 03:51   Re: pg_dump crash on identity sequence with not loaded attributes Tom Lane
• 08:12   Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Tom Lane
• 20:30   Re: postgres 16 index double variable seems to fail. postgres 15 OK Euler Taveira
• 21:29   Re: pg_dump crash on identity sequence with not loaded attributes Tom Lane
• 21:34   Re: pg_dump crash on identity sequence with not loaded attributes Peter Eisentraut
• 23:03   Re: pg_dump crash on identity sequence with not loaded attributes Tom Lane
• 23:54   Re: pg_dump crash on identity sequence with not loaded attributes Artur Zakirov

11 December

• 00:08   Re: pg_dump crash on identity sequence with not loaded attributes Tom Lane
• 00:40   Re: pg_dump crash on identity sequence with not loaded attributes Artur Zakirov
• 03:15   Re: pg_dump crash on identity sequence with not loaded attributes Tom Lane
• 08:43   Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Tom Lane
• 17:38   Re: pg_dump crash on identity sequence with not loaded attributes Artur Zakirov
• 21:48   Re: pg_dump crash on identity sequence with not loaded attributes Tom Lane

12 December

• 02:37   Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Tom Lane
• 02:59   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 03:12   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 03:18   Re: BUG #18745: /src/bin/pg_waldump/compat.c Daniel Gustafsson
• 03:41   Re: pg_dump crash on identity sequence with not loaded attributes Artur Zakirov
• 03:59   "memory exhausted" in query parser/simplifier for many nested parentheses Niklas Hambüchen
• 04:39   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Thomas Munro
• 04:40   Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Tom Lane
• 12:40   Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Laurenz Albe
• 12:47   Re: Problem with constraint unique. Laurenz Albe
• 18:39   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Greg Sabino Mullane
• 20:08   invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 Mike Bayer
• 20:14   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 David G. Johnston
• 20:27   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 jian he
• 20:31   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 jian he
• 20:37   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 David G. Johnston
• 20:55   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 Mike Bayer
• 21:48   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 Tom Lane
• 21:59   Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 Mike Bayer
• 22:05   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Tom Lane
• 22:46   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Niklas Hambüchen
• 23:52   Re: Problem with constraint unique. Mani Sankar

13 December

• 00:34   Re: Problem with constraint unique. Greg Sabino Mullane
• 00:44   Re: Problem with constraint unique. Mani Sankar
• 03:55   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 05:36   Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' Tom Lane
• 07:21   Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
• 08:01   Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan
• 08:16   Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan
• 08:31   Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan
• 09:42   Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
• 18:56   com/ongres/scram/common/exception/ScramException prevents use of postgresql-42.7.2.jar with scram-sha-256 David Gradwell
• 19:03   Re: com/ongres/scram/common/exception/ScramException prevents use of postgresql-42.7.2.jar with scram-sha-256 Daniel Gustafsson
• 19:48   Re: Build failure with GCC 15 (defaults to -std=gnu23) Andrew Dunstan
• 20:26   Re: com/ongres/scram/common/exception/ScramException prevents use of postgresql-42.7.2.jar with scram-sha-256 Dave Cramer
• 20:44   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Greg Sabino Mullane
• 21:11   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Tomas Vondra
• 22:08   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Tom Lane
• 23:06   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Niklas Hambüchen
• 23:43   Re: "memory exhausted" in query parser/simplifier for many nested parentheses David G. Johnston

14 December

• 04:02   Re: "memory exhausted" in query parser/simplifier for many nested parentheses Tom Lane
• 16:46   Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan
• 23:04   Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane

15 December

• 13:04   Re: Build failure with GCC 15 (defaults to -std=gnu23) Robins Tharakan

17 December

• 17:51   to_timestamp function calculation error myzhen
• 21:31   Re: to_timestamp function calculation error Tom Lane

18 December

• 00:01   Is it possible to make ReorderBufferRestoreCleanup faster? Evgeny Kuzin
• 02:29   Not able to restore database - error: could not decompress data: Allocation error : not enough memory Tomasz Szypowski
• 04:15   Surprising SeqScan of appendRel that can't contribute any rows to the result Dmytro Astapov
• 06:08   Re: Surprising SeqScan of appendRel that can't contribute any rows to the result David Rowley
• 06:36   Re: Surprising SeqScan of appendRel that can't contribute any rows to the result Dmytro Astapov
• 07:40   Re: Surprising SeqScan of appendRel that can't contribute any rows to the result Tom Lane
• 08:22   Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory Tom Lane
• 13:12   RE: Not able to restore database - error: could not decompress data: Allocation error : not enough memory Tomasz Szypowski
• 20:25   Re: Incompatibility of newest pg_restore with PostgreSQL-Servers older or equal to version 16 Laurenz Albe
• 21:13   Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory Tom Lane

19 December

• 08:45   Re: Build failure with GCC 15 (defaults to -std=gnu23) Thomas Munro
• 21:44   Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Robert Haas

20 December

• 12:09   BUG #18748: Old name version PG Bug reporting form

21 December

• 01:46   BUG #18749: Error Installing PostgreSQL PG Bug reporting form
• 04:18   Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro

23 December

• 12:13   BUG #18750: Inappropriate update when it is blocked in RC PG Bug reporting form
• 15:53   BUG #18751: Sub-optimal UNION ALL plan PG Bug reporting form
• 16:55   Commit 5a2fed911a broke parallel query Laurenz Albe
• 20:24   Re: BUG #18751: Sub-optimal UNION ALL plan Kirill Reshke
• 21:18   Re: BUG #18751: Sub-optimal UNION ALL plan Tom Lane
• 21:35   Re: Commit 5a2fed911a broke parallel query Tom Lane
• 23:12   Re: Commit 5a2fed911a broke parallel query Tom Lane
• 23:39   Re: Commit 5a2fed911a broke parallel query Laurenz Albe

24 December

• 08:57   Re: BUG #18751: Sub-optimal UNION ALL plan Andrei Lepikhov
• 09:46   Re: BUG #18751: Sub-optimal UNION ALL plan Tom Lane
• 10:36   BUG #18753: Unable to Recover a Deleted Database Using PITR PG Bug reporting form
• 11:43   Corrupt index lead to skipped autovacuum 高偉鈞
• 15:05   Re: BUG #18751: Sub-optimal UNION ALL plan Andrei Lepikhov
• 18:37   Re: BUG #18750: Inappropriate update when it is blocked in RC Pantelis Theodosiou
• 23:24   Re: BUG #18750: Inappropriate update when it is blocked in RC Greg Sabino Mullane

25 December

• 11:32   Re: Re: BUG #18750: Inappropriate update when it is blocked in RC yrshen@stu.xidian.edu.cn
• 11:57   Re: Re: BUG #18750: Inappropriate update when it is blocked in RC yrshen@stu.xidian.edu.cn
• 18:46   Re: Re: BUG #18750: Inappropriate update when it is blocked in RC Pantelis Theodosiou