Re: pg_config_h.in not up-to-date

Поиск
Список
Период
Сортировка
Искать
От
Michael Paquier
Тема
Re: pg_config_h.in not up-to-date
Дата
Msg-id
YC9qEd+zlRBItIyc@paquier.xyz
Ответ на
Список
Дерево обсуждения
pg_config_h.in not up-to-date Antonin Houska <ah@cybertec.at>
Re: pg_config_h.in not up-to-date Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_config_h.in not up-to-date Michael Paquier <michael@paquier.xyz>
Re: pg_config_h.in not up-to-date Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_config_h.in not up-to-date Michael Paquier <michael@paquier.xyz>
Re: pg_config_h.in not up-to-date Tom Lane <tgl@sss.pgh.pa.us>
On Fri, Feb 19, 2021 at 02:21:21AM -0500, Tom Lane wrote:
> Michael Paquier  writes:
> > Indeed, thanks.  It looks like a "git add" that was fat-fingered.  I
> > would like to make things more consistent with the attached.
> 
> +1, but I think the first period in this comment is redundant:
> 
> +  AC_DEFINE([USE_OPENSSL], 1, [Define to 1 to build with OpenSSL support. (--with-ssl=openssl).])

I guess that you mean the second period here to be more consistent
with the others?  That would mean the following diff:
+  AC_DEFINE([USE_OPENSSL], 1, [Define to 1 to build with OpenSSL support. (--with-ssl=openssl)])
--
Michael
В списке pgsql-hackers по дате отправления
От: Amit Langote
Дата:
От: David Rowley
Дата:
Сообщение: Re: Tid scan improvements
FAQ