Re: potentially missed pgindent in REL_19_STABLE - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: potentially missed pgindent in REL_19_STABLE
Date
Msg-id 01DBBD2E-2029-44ED-8FC1-D5767B7BD373@yesql.se
Whole thread
In response to potentially missed pgindent in REL_19_STABLE  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: potentially missed pgindent in REL_19_STABLE
List pgsql-hackers
> On 24 Sep 2026, at 10:23, Amit Langote <amitlangote09@gmail.com> wrote:

> I wonder if I'm the only one seeing $subject, like this:
> ...
> Does anyone object to applying the attached to fix that?

I did see it, but it was during a freeze and then it slipped my mind.  Shipping
a pgindent clean tree clearly has value, will there would be a tree-wide
pgindent run before tagging REL_19_0?

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten
Next
From: vignesh C
Date:
Subject: Re: Up to 50x degradation in dblink performance when receiving notice traffic 19 vs 18