From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Piotr Stefaniak <postgres@piotr-stefaniak.me>
Subject: Re: Preliminary results for proposed new pgindent implementation
Date: Fri, 19 May 2017 09:30:08 -0700
Message-ID: <20170519163008.6algqcf66ldu2bxa@alap3.anarazel.de> (raw)
In-Reply-To: <CA+TgmoYXsn6=664yUp90y-Xt8ZUD7uh19naybjJBaqO-KDUOCQ@mail.gmail.com>
References: <30527.1495162840@sss.pgh.pa.us>
<CA+TgmoamXhAoKY+pPSfGiu=3q6u-+1EOksdPimGS8YuqNuaSYQ@mail.gmail.com>
<26654.1495203668@sss.pgh.pa.us>
<20170519150526.GX3151@tamriel.snowman.net>
<29626.1495207374@sss.pgh.pa.us>
<CA+TgmoYXsn6=664yUp90y-Xt8ZUD7uh19naybjJBaqO-KDUOCQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 2017-05-19 12:21:52 -0400, Robert Haas wrote:
> On Fri, May 19, 2017 at 11:22 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > I certainly would rather that our version matched something that's under
> > active maintenance someplace. But it seems like there are two good
> > arguments for having a copy in our tree:
> >
> > * easy accessibility for PG developers
> >
> > * at any given time we need to be using a specific "blessed" version,
> > so that all developers can get equivalent results. There's pretty much
> > no chance of that happening if we depend on distro-provided packages,
> > even if those share a common upstream.
>
> Yeah, but those advantages could also be gained by putting the
> pgindent tree on git.postgresql.org in a separate repository. Having
> it in the same repository as the actual PostgreSQL code is not
> required nor, in my opinion, particularly desirable.
I'm of the contrary opinion. A lot of the regular churn due to pgindent
right now is because it's inconvenient to run. Having to clone a
separate repository, compile that project, put it into PATH (fun if
there's multiple versions), run pgindent, discover typedefs.list is out
of date, update, run, ... is pretty much a guarantee that'll continue.
If we had a make indent that computed local typedefs list, *added* new
but not removed old ones, we could get much closer to just always being
properly indented.
The cost of putting it somewhere blow src/tools/pgindent seems fairly
minor.
- Andres
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: pgsql-hackers@postgresql.org
Cc: andres@anarazel.de, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, sfrost@snowman.net, postgres@piotr-stefaniak.me
Subject: Re: Preliminary results for proposed new pgindent implementation
In-Reply-To: <20170519163008.6algqcf66ldu2bxa@alap3.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox