Re: Exposing PG_VERSION_NUM in pg_config
От | Michael Paquier |
---|---|
Тема | Re: Exposing PG_VERSION_NUM in pg_config |
Дата | |
Msg-id | CAB7nPqRLjSo4FhYoBkuArqULmH-9EeDKufe+UtNMLbmjTOtddw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Exposing PG_VERSION_NUM in pg_config (Michael Paquier <michael.paquier@gmail.com>) |
Список | pgsql-hackers |
On Wed, Mar 25, 2015 at 2:32 PM, Michael Paquier <michael.paquier@gmail.com> wrote: > On Wed, Mar 25, 2015 at 8:26 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Hm. We're all agreed that there's a use case for exposing PG_VERSION_NUM >> to the makefiles, but I did not hear one for adding it to pg_config; and >> doing the former takes about two lines whereas adding a pg_config option >> entails quite a lot of overhead (documentation, translatable help text, >> yadda yadda). So I'm not in favor of doing the latter without a much >> more solid case than has been made. > > Well, I have no other cases than ones of the type mentioned upthread, > and honestly I am fine as long as we do not apply maths to a version > string. So attached is a patch that adds VERSION_NUM in > Makefile.global. Added entry in CF 2015-06 to not have this stuff fall into the void: https://commitfest.postgresql.org/5/203/ -- Michael
В списке pgsql-hackers по дате отправления: