| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: perltidy version |
| Date: | 2018-04-23 15:43:06 |
| Message-ID: | dcdeb762-235c-8ab0-e336-832101c6e5a8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/5/18 09:02, Magnus Hagander wrote:
> I think we should just pick some recent one and use it for X years; use
> that one for all backbranches. I propose X=3. I propose 20170521
> (newer ones seem to cater for stuff that I think we mostly don't use).
>
>
> 20140328 seems to cover *most* versions. Another argument for that one
> would be it's the one that we have on Borka, which is where we build the
> official release tarballs, so we can use that as a stable fallback.
>
> Those are both fairly weak arguments though. As long as we have good
> instructions for how to make a local install of it that doesn't affect
> the rest of the system, then that should not matter. And we need such
> instructions anyway, since it won't be on every distribution.
Did we decide on this?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-04-23 15:58:41 | Re: perltidy version |
| Previous Message | Andres Freund | 2018-04-23 15:42:53 | Re: Make description of heap records more talkative for flags |