| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_recvlogical: honor source cluster file permissions for output files |
| Date: | 2026-05-18 10:47:15 |
| Message-ID: | CAHGQGwHz8aOjPbJd+mCb=OuYdfZQ-RkeatuQrfDCE4cqJxt69w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 17, 2026 at 12:22 AM Srinath Reddy Sadipiralla
<srinath2133(at)gmail(dot)com> wrote:
> i have reviewed, tested the patch and it LGTM,
Thanks for the review!
> i think we can add
> a TAP test to verify the group permission, attached a diff patch
> for the same,
Thanks for the patch!
The test you added checks that pg_recvlogical creates output files with
mode 0640 when the cluster is initialized with group access enabled.
However, it does not check the opposite case, i.e., that pg_recvlogical
creates output files with mode 0600 when group access is disabled.
It seems we should test both cases, similar to what 010_basebackup.pl does?
As far as I can tell, 010_basebackup.pl initializes the cluster without group
access and checks the backup permissions, then enables group access using
chmod_recursive() and verifies that group permissions are also applied to
the backup. I updated the TAP test following this approach and attached
a revised patch.
>> I think this should be backpatched to all supported branches.
>
>
> +1
I'm currently thinking of backpatching the fix itself to all supported branches,
but adding the test only to master. Because it does not seem worthwhile to
spend much time backporting the test to older branches, where the test code
differs much from master. Thought?
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-05-18 10:48:57 | Re: pg_recvlogical: honor source cluster file permissions for output files |
| Previous Message | Ajin Cherian | 2026-05-18 10:42:39 | Re: [PATCH] Preserve replication origin OIDs in pg_upgrade |