Re: Improve pgindent's formatting named fields in struct literals and varidic functions - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Improve pgindent's formatting named fields in struct literals and varidic functions
Date
Msg-id 71e9889c-86be-4084-a5ae-fc535221b5fb@proxel.se
Whole thread Raw
In response to Re: Improve pgindent's formatting named fields in struct literals and varidic functions  (Andreas Karlsson <andreas@proxel.se>)
List pgsql-hackers
On 3/31/26 8:57 PM, Andreas Karlsson wrote:
> 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.
Rebased patch on top of HEAD.

Andreas

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Next
From: Tomas Vondra
Date:
Subject: Re: Change default of jit to off