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

From Peter Eisentraut
Subject Re: pgindent vs. git whitespace check
Date
Msg-id 88a42542-4661-97ec-5c76-4421f6a91c38@enterprisedb.com
Whole thread Raw
In response to Re: pgindent vs. git whitespace check  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On 22.02.23 15:49, Alvaro Herrera wrote:
> 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.

Fixed this way.




pgsql-hackers by date:

Previous
From: Noel Grandin
Date:
Subject: how does postgresql handle LOB/CLOB/BLOB column data that dies before the query ends
Next
From: Alvaro Herrera
Date:
Subject: Re: PATCH: Using BRIN indexes for sorted output