From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Dominique Devienne <ddevienne(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: No default for (user-specific) service file location on Windows? |
Date: | 2022-05-19 14:11:06 |
Message-ID: | 164663.1652969466@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> We can't change the default file in older branches obviously, but I'd be a bit
> worried about changing the default in the next major version either as it would
> add unnecessary pain for users that do know and rely on the current default. I
> guess we have to live with it, and properly document it.
Yeah, agreed. Documentation fix seems like the way to go.
I do not like your proposed wording, as it seems way too dense.
Can't we avoid the parenthetical remarks (plural) inside a sub-clause?
You're asking the reader to keep track of about three levels of
interrupt.
Maybe just put the Windows info in a separate sentence:
... located at ~/.pg_service.conf</filename>.
On Microsoft Windows, it is located at
%APPDATA%\postgresql\.pg_service.conf, where %APPDATA% means the
Application Data subdirectory in the user's profile.
In either case, the location can be overridden by setting ...
ISTR there's precedent elsewhere for doing it about like that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2022-05-19 15:47:12 | Re: In case of network issues, how long before archive_command does retries |
Previous Message | Koen De Groote | 2022-05-19 13:43:38 | Re: In case of network issues, how long before archive_command does retries |