Re: Exposing PG_VERSION_NUM in pg_config

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Exposing PG_VERSION_NUM in pg_config
Дата
Msg-id 17371.1427309444@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Exposing PG_VERSION_NUM in pg_config  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: Exposing PG_VERSION_NUM in pg_config  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> On 3/24/15 6:26 PM, Tom Lane 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.

> Why else would you want the version number other than to do some kind of 
> comparison?

The question is why, if we supply the version number in a make variable,
you would not just use that variable instead of having to do
"$(shell $(PG_CONFIG) --something)".  The shell version adds new failure
modes, removes none, and has no redeeming social value that I can see.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: deparsing utility commands
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Exposing PG_VERSION_NUM in pg_config