| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Jelte Fennema <postgres(at)jeltef(dot)nl>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: running logical replication as the subscription owner |
| Date: | 2023-05-12 03:39:44 |
| Message-ID: | CAD21AoDPbWQbC-eN2jvt89zTzeUqz6Nx9QvpyBNMyM28DQxzcg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 12, 2023 at 1:12 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, May 11, 2023 at 7:38 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> > Do we want the initial sync to also respect 'run_as_owner' option? I
> > might be missing something but I don't see anything in the docs about
> > initial sync interaction with this option. In the commit a2ab9c06ea,
> > we did the permission checking during the initial sync so I thought we
> > should do it here as well.
>
> It definitely should work that way. lf it doesn't, that's a bug.
After some tests, it seems that the initial sync worker respects
'run_as_owner' during catching up but not during COPYing.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-05-12 03:48:12 | RE: Time delayed LR (WAS Re: logical replication restrictions) |
| Previous Message | Masahiko Sawada | 2023-05-12 02:07:38 | Re: Time delayed LR (WAS Re: logical replication restrictions) |