Re: ProcessStartupPacket(): database_name and user_name truncation

Поиск
Список
Период
Сортировка
От Drouvot, Bertrand
Тема Re: ProcessStartupPacket(): database_name and user_name truncation
Дата
Msg-id 230a77dd-808b-0bb3-9008-7c9db3fddf25@gmail.com
обсуждение исходный текст
Ответ на Re: ProcessStartupPacket(): database_name and user_name truncation  ("Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>)
Ответы Re: ProcessStartupPacket(): database_name and user_name truncation  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Re: ProcessStartupPacket(): database_name and user_name truncation  (Nathan Bossart <nathandbossart@gmail.com>)
Список pgsql-hackers
Hi,

On 6/30/23 7:32 PM, Drouvot, Bertrand wrote:
> 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.
> 

Please find V2 attached where it's failing as soon as the database name or
user name are detected as overlength.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tomas Vondra
Дата:
Сообщение: possible bug in handling of contrecords in dd38ff28ad (Fix recovery_prefetch with low maintenance_io_concurrency)
Следующее
От: Joseph Koshakow
Дата:
Сообщение: Re: Preventing non-superusers from altering session authorization