Re: [HACKERS] show precise repos version for dev builds?
От | Craig Ringer |
---|---|
Тема | Re: [HACKERS] show precise repos version for dev builds? |
Дата | |
Msg-id | CAMsr+YFnAoDHtSF8dKZLj6e5nRLuztbrss3VDRpTo++xnf7x5A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] show precise repos version for dev builds? (Jeremy Schneider <schneider@ardentperf.com>) |
Ответы |
Re: [HACKERS] show precise repos version for dev builds?
Re: [HACKERS] show precise repos version for dev builds? |
Список | pgsql-hackers |
On 11 October 2017 at 11:44, Jeremy Schneider <schneider@ardentperf.com> wrote: > On Sun, Oct 1, 2017 at 8:10 AM, Tom Lane <tgl@sss.pgh.pa.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: