Mailing lists [pgsql-bugs]

20 November

• 00:48   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 01:33   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 04:34   Re: BUG #18715: replace() function silently fails if 3rd argument is null Erik Wienhold
• 04:40   Re: BUG #18715: replace() function silently fails if 3rd argument is null Tom Lane
• 04:50   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 05:09   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 05:15   Re: [EXTERNAL] Re: BUG #18707: Installation issue Thomas Munro
• 05:31   Re: BUG #18715: replace() function silently fails if 3rd argument is null Erik Wienhold
• 09:31   RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 Bing Xu
• 09:47   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 09:52   Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 David G. Johnston
• 10:05   RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 Bing Xu
• 10:21   Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 David G. Johnston
• 10:23   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 11:11   'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5 Aya Iwata (Fujitsu)
• 12:06   BUG #18716: I wanted to upload/restore tar file data, While uploading file facing error, image attached. PG Bug reporting form
• 12:27   Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5 Noah Misch
• 13:49   Wrong german error message encoding 
• 14:17   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
• 14:35   Re: Build failure with GCC 15 (defaults to -std=gnu23) Peter Eisentraut
• 14:38   Re: Sorting Discrepancy in PostgreSQL 14.13 Peter Eisentraut
• 15:00   Re: Wrong german error message encoding Daniel Gustafsson
• 17:16   Can not open Postgre SQL 17.1 after update Большой Сэм
• 18:33   BUG #18717: ALTER ROLE SET ROLE functionality is broken PG Bug reporting form
• 19:30   Re: Today's Postgres Releases break login roles Etienne LAFARGE
• 21:10   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 21:20   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
• 21:32   Re: Build failure with GCC 15 (defaults to -std=gnu23) Tom Lane
• 21:32   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 21:35   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 21:39   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 21:48   Re: BUG #18717: ALTER ROLE SET ROLE functionality is broken Nathan Bossart
• 21:54   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 22:02   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Bertrand Drouvot
• 22:02   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart
• 22:29   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Tom Lane
• 22:50   Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails Nathan Bossart