Re: potentially missed pgindent in REL_19_STABLE

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: potentially missed pgindent in REL_19_STABLE
Date: 2026-09-24 08:33:17
Message-ID: 01DBBD2E-2029-44ED-8FC1-D5767B7BD373@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 24 Sep 2026, at 10:23, Amit Langote <amitlangote09(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-09-24 08:38:52 Re: Up to 50x degradation in dblink performance when receiving notice traffic 19 vs 18
Previous Message Thom Brown 2026-09-24 08:32:36 Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten