From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Questions about the new subscription parameter: password_required |
Date: | 2023-09-26 17:53:22 |
Message-ID: | CA+TgmoZR5GWUzNWeHmdMfi0Ux48YDaUojZqyh1z8rRwjPmk+=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 26, 2023 at 1:00 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> As I said earlier, I think the best thing to do is to just have a
> section that describes when to use password_required, what specific
> things you should do to satisfy that case, and what caveats you should
> avoid. Something like:
>
> "If you want to have a subscription using a connection string without
> a password managed by a non-superuser, then: [ insert SQL steps here ].
> Warning: if the connection string doesn't contain a password, make sure
> to set password_required=false before transferring ownership, otherwise
> it will start failing."
>
> Documenting the behavior is good, too, but I find the behavior
> difficult to document, so examples will help.
Yeah, I think something like that could make sense, with an
appropriate amount of word-smithing.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-09-26 18:01:23 | Re: [PGdocs] fix description for handling pf non-ASCII characters |
Previous Message | Robert Haas | 2023-09-26 17:49:32 | Re: Eager page freeze criteria clarification |