Message-ID: <9a949301-eb31-4245-aef5-6ced20716ec4@proxel.se>
Date: Tue, 31 Mar 2026 20:57:48 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Improve pgindent's formatting named fields in struct literals and
 varidic functions
To: Tom Lane <tgl@sss.pgh.pa.us>, =?UTF-8?Q?=C3=81lvaro_Herrera?=
 <alvherre@kurilemu.de>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <202603311716.cribie6xvxhn@alvherre.pgsql>
 <2737243.1774980800@sss.pgh.pa.us>
From: Andreas Karlsson <andreas@proxel.se>
Content-Language: en-US
In-Reply-To: <2737243.1774980800@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/9a949301-eb31-4245-aef5-6ced20716ec4%40proxel.se>
Precedence: bulk

On 3/31/26 8:13 PM, Tom Lane wrote:
> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
>> I think the best time to get it in is a few weeks after the feature
>> freeze.  That way we minimize the impact on any fixes during the
>> stabilization period.  I'm not sure at what point relative to the betas
>> though; is it better to do it before, so that we have a chance to fix
>> any possible problems before they hit users, or is it better to do after
>> beta1, so that patches that we discover need reverting for pg19 have
>> already had a chance to be so?
> 
> [...]
> 
> So we haven't been totally consistent about it, but mid-May (a couple
> weeks before making the new branch) seems like the usual choice.
Makes sense to merge it while the tree is less noisy. Especially right 
now might be the most annoying time possible.

Andreas