Re: [16+] subscription can end up in inconsistent state
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Jeff Davis <pgsql@j-davis.com>, Amit Kapila <amit.kapila16@gmail.com>, pgsql-bugs@postgresql.org
Date: 2023-11-27T04:56:12Z
Lists: pgsql-bugs
Attachments
- v6-0001-A-non-superuser-is-only-allowed-to-specify-the-pa.patch (text/x-patch) patch v6-0001
On Fri, 6 Oct 2023 at 12:26, Peter Smith <smithpb2250@gmail.com> wrote: > > On Thu, Oct 5, 2023 at 9:50 PM vignesh C <vignesh21@gmail.com> wrote: > > > > > > 3. Connection string option 'passfile'? > > > > > > IIUC the subscription "password_required" option means that the > > > password must be in the connection string. I'm not sure how the other > > > connection string "passfile" option [2] fits into this rule. The > > > current patch looks like it would reject the passfile option (because > > > IIUC libpqrcv_check_conninfo only looks for "password") -- is it > > > deliberate? And, should it be documented/commented somewhere? > > > > > > ====== > > > src/backend/replication/libpqwalreceiver/libpqwalreceiver.c > > > > I felt we should not allow password from the passfile for > > non-superusers, if password_required is true, the password can be > > specified only through the password option of the connection string. > > The same has been documented. > > > > Assuming that everybody is happy with the above decision to only allow > the 'password' parameter, then your latest v5-0001 patch looked good > to me. The patch was not applying on HEAD because of recent commits, the attached v6 version patch is rebased on top of HEAD. Regards, Vignesh
Commits
-
Fix buildfarm error from commit 5c31669058.
- 5b5318c38745 16.2 landed
- dd3ca8cbb014 17.0 landed
-
Re-validate connection string in libpqrcv_connect().
- 4c03ac7e2bc4 16.2 landed
- 5c31669058b5 17.0 landed