Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
| От | Bertrand Drouvot | 
|---|---|
| Тема | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails | 
| Дата | |
| Msg-id | Zz3+TWanHHjBUErS@ip-10-97-1-34.eu-west-3.compute.internal обсуждение исходный текст  | 
		
| Ответ на | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails (Tom Lane <tgl@sss.pgh.pa.us>) | 
| Ответы | 
                	
            		Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
            		
            		 | 
		
| Список | pgsql-bugs | 
Hi, On Wed, Nov 20, 2024 at 10:10:51AM -0500, Tom Lane wrote: > Bertrand Drouvot <bertranddrouvot.pg@gmail.com> writes: > > Could we rely on pg_encoding_max_length() instead of MAX_MULTIBYTE_CHAR_LEN? That > > would then work for short characters too IIUC. > > No. We don't know which encoding it is. Even if you wanted to say > "use the database encoding", we haven't identified the database yet. I had in mind to "fully scan" pg_database in GetDatabaseTuple(), get the datname and encoding from FormData_pg_database and start from there the comparison with the dbname passed as an argument to GetDatabaseTuple(). Thoughts? Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-bugs по дате отправления: