Re: run pgindent in CI

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: run pgindent in CI
Date: 2026-09-22 14:04:12
Message-ID: 1178258.1790085852@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2026-09-22 Tu 3:10 AM, Peter Eisentraut wrote:
>> One surprise from this is that this generates a massive pgindent diff
>> against the current tree, because there are a bunch of entries missing
>> or wrong in src/tools/pgindent/exclude_file_patterns.  I guess most
>> people don't see this because these are mostly generated files, which
>> would get reindented but then ignored via gitignore, but if you run
>> pgindent --check --diff, then this will show up.

> [koel] just runs:
>    src/tools/pgindent/pgindent --diff --check .
> Of course, that's against a pure source tree.

Yeah, I generally run pgindent against a clean tree as well. We have
made some efforts to make generated files be pgindent-clean, but
it's been pretty haphazard, and I doubt we want to make a project
policy requiring that. So really the right thing is to make this
CI module do likewise.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ZizhuanLiu X-MAN 2026-09-22 14:11:49 Re: Optimize MCV stats for sortable types and utilize sorted-order properties
Previous Message Bertrand Drouvot 2026-09-22 14:03:02 Re: Add a permission check to pg_stat_get_backend_subxact()