| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, adam(at)labkey(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
| Date: | 2024-11-27 18:17:18 |
| Message-ID: | 1896106.1732731438@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> writes:
> Indeed, reverting might be the way to go then (without waiting for more 17
> behavior reports).
I have an idea that might salvage something from what we've just
been doing. The biggest single problem with the old behavior,
AIUI, was the possibility of sending back encoding-corrupt names
in connection failure reports. How about something like:
* Don't truncate the names on sight (so we keep 562bee0fc1).
* Truncate the names at NAMEDATALEN-1 just before catalog lookup
(this restores the old lookup behavior, solving the current report).
* In lookup-failure messages, be sure to report the un-truncated
name (avoiding the bad-encoding problem).
* Copy the correctly-truncated names from the catalog to any
persistent storage such as MyProcPort, so that those are used
for all post-connection purposes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-11-27 18:28:24 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Previous Message | PG Bug reporting form | 2024-11-27 18:15:20 | BUG #18728: Inconsistency between pg_wait_events.name and pg_stat_activity.wait_event for LWLocks |