| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgindent vs. git whitespace check |
| Date: | 2023-02-24 15:03:29 |
| Message-ID: | 88a42542-4661-97ec-5c76-4421f6a91c38@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-02-24 15:14:16 | Re: PATCH: Using BRIN indexes for sorted output |
| Previous Message | Noel Grandin | 2023-02-24 13:31:39 | how does postgresql handle LOB/CLOB/BLOB column data that dies before the query ends |