Re: ProcessStartupPacket(): database_name and user_name truncation

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-22 06:10:30
Message-ID: c1a57fab-ef09-31f2-db16-172df19af453@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 6/22/23 1:37 AM, Michael Paquier wrote:
> On Wed, Jun 21, 2023 at 12:55:15PM -0700, Nathan Bossart wrote:
>> LGTM. I think this can wait for v17 since the current behavior has been
>> around since 2001 and AFAIK this is the first report. While it's arguably
>> a bug fix, the patch also breaks some cases that work today.
>
> Agreed that anything discussed on this thread does not warrant a
> backpatch.

Fully agree, the CF entry [1] has been tagged as "Target Version 17".

[1] https://commitfest.postgresql.org/43/4383/

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 Amit Kapila 2023-06-22 06:24:24 Re: [DOC] Update ALTER SUBSCRIPTION documentation v3
Previous Message Yugo NAGATA 2023-06-22 05:58:14 Re: Make pgbench exit on SIGINT more reliably