Re: Suggestions for improving \conninfo output in v18 - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Suggestions for improving \conninfo output in v18
Date
Msg-id 2ab7121b-6c7d-493d-9008-ed440d92add5@oss.nttdata.com
Whole thread Raw
In response to Re: Suggestions for improving \conninfo output in v18  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers

On 2025/06/13 22:50, Nathan Bossart wrote:
> On Fri, Jun 13, 2025 at 06:52:26PM +0900, Fujii Masao wrote:
>> I've added the RMT to CC. What do you think about including the 0001 patch in v18?
>> Would you be okay with that?
>>
>> -----------------------
>> The 0001 patch changes \conninfo to report the full protocol version (e.g., 3.2)
>> instead of just the major version (e.g., 3). This is technically a behavior change,
>> but since protocol version 3.2 was introduced in v18, and both 3.0 and 3.2 are
>> now valid, always showing just "3" isn't very helpful. To see which protocol
>> version is actually in use, showing the full version is more informative.
>>
>> Therefore I see this as fixing an oversight in commit bba2fbc6238, so I'd like to
>> commit the 0001 patch as well in v18. Thought?
>> -----------------------
> 
> Sounds good to me.

Thanks for confirming! I've now pushed the 0001 patch.

As discussed earlier, I've also committed the 0002 patch.

Regards,

-- 
Fujii Masao
NTT DATA Japan Corporation




pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [PING] [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward
Next
From: Corey Huinker
Date:
Subject: Re: pg_dump --with-* options