Re: ProcessStartupPacket(): database_name and user_name truncation - Mailing list pgsql-hackers

From Drouvot, Bertrand
Subject Re: ProcessStartupPacket(): database_name and user_name truncation
Date
Msg-id 073e95fa-8413-8afd-3eba-01aea47198f7@gmail.com
Whole thread Raw
In response to Re: ProcessStartupPacket(): database_name and user_name truncation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ProcessStartupPacket(): database_name and user_name truncation
Re: ProcessStartupPacket(): database_name and user_name truncation
List pgsql-hackers
Hi,

On 6/30/23 5:54 PM, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> After taking another look at this, I wonder if it'd be better to fail as
>> soon as we see the database or user name is too long instead of lugging
>> them around when authentication is destined to fail.
> 
> If we're agreed that we aren't going to truncate these identifiers,
> that seems like a reasonable way to handle it.
> 

Yeah agree, thanks Nathan for the idea.
I'll work on a new patch version proposal.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SPI isolation changes
Next
From: David Christensen
Date:
Subject: Initdb-time block size specification