Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:12:10
Message-ID: Z0dg-nEyir1yM2nb@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 27, 2024 at 06:03:43PM +0000, Bertrand Drouvot wrote:
> Indeed, reverting might be the way to go then (without waiting for more 17
> behavior reports).

Okay. I'll plan on reverting it early next week.

--
nathan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next 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
Previous Message Tom Lane 2024-11-27 18:11:00 Re: BUG #18725: "set role" requires "grant connect on database"