public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Jelte Fennema <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Justin Pryzby <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Noah Misch <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Stephen Frost <[email protected]>
Cc: Jesse Zhang <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Subject: Re: run pgindent on a regular basis / scripted manner
Date: Sat, 22 Apr 2023 10:12:06 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEwjuNTSfV3251RSUt2SwW26CS5vrazs1DwYq2VqQo+dGw@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CAGECzQRJrcoxozHh=BRTdLrirFui-3nvdRZru7GGa4F9HJV2Rw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CAGECzQSUYmfTwEWcVfwb4d=vf=M7RYJjq6ie0YPTUhP+YFcEww@mail.gmail.com>
	<[email protected]>
	<OSZPR01MB63100E1C06045FB66B16728BFDA09@OSZPR01MB6310.jpnprd01.prod.outlook.com>
	<[email protected]>
	<CAGECzQSu6mLzPhd7csBfnXtW9kfoVRn5TWFH1fPGMc4mpkHyOw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CABUevEwjuNTSfV3251RSUt2SwW26CS5vrazs1DwYq2VqQo+dGw@mail.gmail.com>


On 2023-04-22 Sa 08:47, Magnus Hagander wrote:
> On Sat, Apr 22, 2023 at 1:42 PM Andrew Dunstan<[email protected]>  wrote:
>>
>> On 2023-04-22 Sa 04:50, Michael Paquier wrote:
>>
>> On Fri, Apr 21, 2023 at 09:58:17AM +0200, Jelte Fennema wrote:
>>
>> For 2 the upstream thread listed two approaches:
>> a. Install a pre-receive git hook on the git server that rejects
>> pushes to master that are not indented
>> b. Add a test suite that checks if the code is correctly indented, so
>> the build farm would complain about it. (Suggested by Peter E)
>>
>> I think both a and b would work to achieve 2. But as Peter E said, b
>> indeed sounds like less of a divergence of the status quo. So my vote
>> would be for b.
>>
>> FWIW, I think that there is value for both of them.  Anyway, isn't 'a'
>> exactly the same as 'b' in design?  Both require a build of
>> pg_bsd_indent, meaning that 'a' would also need to run an equivalent
>> of the regression test suite, but it would be actually costly
>> especially if pg_bsd_indent itself is patched.  I think that getting
>> more noisy on this matter with 'b' would be enough, but as an extra
>> PG_TEST_EXTRA for committers to set.
>>
>> Such a test suite would need a dependency to the 'git' command itself,
>> which is not something that could be safely run in a release tarball,
>> in any case.
>>
>>
>> Perhaps we should start with a buildfarm module, which would run pg_indent --show-diff. That would only need to run on one animal, so a failure wouldn't send the whole buildfarm red. This would be pretty easy to do.
>
> Just to be clear, you guys are aware we  already have a git repo
> that's supposed to track "head + pg_indent" at
> https://git.postgresql.org/gitweb/?p=postgresql-pgindent.git;a=shortlog;h=refs/heads/master-pgindent
> right?
>
> I see it is currently not working and this has not been noticed by
> anyone, so I guess it kind of indicates nobody is using it today. The
> reason appears to be that it uses pg_bsd_indent that's in our apt
> repos and that's 2.1.1 and not 2.1.2 at this point. But if this is a
> service that would actually be useful, this could certainly be ficked
> pretty easy.
>
> But bottom line is that if pgindent is as predictable as it should be,
> it might be easier to use that one central place that already does it
> rather than have to build a buildfarm module?
>

Now that pg_bsd_indent is in the core code why not just use that?


Happy if you can make something work without further effort on my part :-)


cheers


andew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

view thread (142+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: run pgindent on a regular basis / scripted manner
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox