From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: show precise repos version for dev builds? |
Date: | 2017-10-11 22:46:19 |
Message-ID: | 9e91fd3f-a912-0ddc-699d-ca785c232e40@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/11/17 04:19, Craig Ringer wrote:
> On 11 October 2017 at 11:44, Jeremy Schneider <schneider(at)ardentperf(dot)com> wrote:
>> On Sun, Oct 1, 2017 at 8:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>
>>> configure --with-extra-version=whateveryouwant
>>
>> I see that this build option has been around since 9.4; is anyone
>> using it to mark patched production builds? EnterpriseDB or
>> 2ndQuadrant? How about the cloud providers?
>
> We started using it for BDR, but unfortunately too much software
> explodes spectacularly when you use it, due to simplistic/buggy
> version parsing.
I've been using
--with-extra-version=+git`date +%Y%m%d`"~"`git rev-parse --short HEAD`
for my local builds for some time, and I've not experienced any such
problems.
However, using the various numeric reporting options is clearly better
if you want to do version comparisons. The "extra version" stuff should
be mainly for labeling.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2017-10-11 22:52:31 | Re: Fix a typo in execReplication.c |
Previous Message | Lukas Fittl | 2017-10-11 22:23:07 | Re: [HACKERS] Re: BUG #14821: idle_in_transaction_session_timeout sometimes gets ignored when statement timeout is pending |