Re: pgindent vs. git whitespace check - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pgindent vs. git whitespace check
Date
Msg-id 20230222144948.svf2szymuqbjfebs@alvherre.pgsql
Whole thread Raw
In response to pgindent vs. git whitespace check  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: pgindent vs. git whitespace check
List 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 by date:

Previous
From: Maxim Orlov
Date:
Subject: Re: Add SHELL_EXIT_CODE to psql
Next
From: Tom Lane
Date:
Subject: Re: pgindent vs. git whitespace check