Re: pgindent vs. git whitespace check
От | Alvaro Herrera |
---|---|
Тема | Re: pgindent vs. git whitespace check |
Дата | |
Msg-id | 20230222144948.svf2szymuqbjfebs@alvherre.pgsql обсуждение исходный текст |
Ответ на | pgindent vs. git whitespace check (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: pgindent vs. git whitespace check
|
Список | pgsql-hackers |
On 2023-Feb-22, Peter Eisentraut wrote: > In the meantime, I suggest we work around this, perhaps by > > conn = libpqsrv_connect_params(keywords, values, /* expand_dbname = */ false, > PG_WAIT_EXTENSION); I suggest conn = libpqsrv_connect_params(keywords, values, false, /* expand_dbname */ PG_WAIT_EXTENSION); which is what we typically do elsewhere and doesn't go overlength. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ Maybe there's lots of data loss but the records of data loss are also lost. (Lincoln Yeoh)
В списке pgsql-hackers по дате отправления: