| From: | Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Questions about the new subscription parameter: password_required |
| Date: | 2023-10-13 09:18:33 |
| Message-ID: | 8a591918-6eba-9314-a3f0-ad22406e50d0@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/23/23 03:57, Jeff Davis wrote:
> IIUC there is really one use case here, which is for superuser to
> define a subscription including the connection, and then change the
> owner to a non-superuser to actually run it (without being able to
> touch the connection string itself). I'd just document that in its own
> section, and mention a few caveats / mistakes to avoid. For instance,
> when the superuser is defining the connection, don't forget to set
> password_required=false, so that when you reassign to a non-superuser
> then the connection doesn't break.
Hi,
I tried adding a section in "Logical Replication > Subscription" with
the text you suggested and links in the CREATE / ALTER SUBSRIPTION commands.
Is it better ?
--
Benoit Lobréau
Consultant
http://dalibo.com
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Doc-patch-for-password_required.patch | text/x-patch | 3.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2023-10-13 09:21:58 | Re: BRIN minmax multi - incorrect distance for infinite timestamp/date |
| Previous Message | Dmitry Dolgov | 2023-10-13 09:06:21 | Re: LLVM 16 (opaque pointers) |