Re: ProcessStartupPacket(): database_name and user_name truncation

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: ProcessStartupPacket(): database_name and user_name truncation
Date: 2023-06-30 17:32:50
Message-ID: 073e95fa-8413-8afd-3eba-01aea47198f7@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 6/30/23 5:54 PM, Tom Lane wrote:
> Nathan Bossart <nathandbossart(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Christensen 2023-06-30 17:35:09 Initdb-time block size specification
Previous Message Tom Lane 2023-06-30 16:47:10 Re: SPI isolation changes