| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgindent vs. git whitespace check |
| Date: | 2023-02-22 14:49:48 |
| Message-ID: | 20230222144948.svf2szymuqbjfebs@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-22 14:52:14 | Re: pgindent vs. git whitespace check |
| Previous Message | Maxim Orlov | 2023-02-22 14:43:45 | Re: Add SHELL_EXIT_CODE to psql |