| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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 08:19:56 |
| Message-ID: | CAMsr+YFnAoDHtSF8dKZLj6e5nRLuztbrss3VDRpTo++xnf7x5A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
This led me to push for wider adoption of server_version_num - in
particular, exposing it as an initial connection parameter via
GUC_REPORT, and exposing it in pg_config. After a few attempts I've
given up on that as a lost cause now, though I still disagree with the
rationale.
Right now, if you use it, various 3rd party software will fail in a
variety of exciting ways, some more subtle than others.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-10-11 08:53:56 | Re: SendRowDescriptionMessage() is slow for queries with a lot of columns |
| Previous Message | Haribabu Kommi | 2017-10-11 07:30:49 | Re: utility commands benefiting from parallel plan |