| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Önder Kalacı <onderkalaci(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL |
| Date: | 2023-07-10 03:35:49 |
| Message-ID: | TYAPR01MB5866CFDF4BE649C3163B894FF530A@TYAPR01MB5866.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Amit,
> > Yes, I agree, it is (and was before my patch as well) un-documented
> limitation of REPLICA IDENTITY FULL.
> > And, as far as I can see, my patch actually didn't have any impact on the
> limitation. The unsupported
> > cases are still unsupported, but now the same error is thrown in a slightly
> different place.
> > I think that is a minor limitation, but maybe should be listed [1]?
> > >
>
> +1.
>
> >
> > Yes, your modification did not touch the restriction. It has existed before the
> > commit. I (or my colleague) will post the patch to add the description, maybe
> > after [1] is committed.
> >
>
> I don't think there is any dependency between the two. So, feel free
> to post the patch separately.
Okay, thank you for your confirmation. I have started the fork thread [1].
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-07-10 03:36:22 | Re: Synchronizing slots from primary to standby |
| Previous Message | Hayato Kuroda (Fujitsu) | 2023-07-10 03:33:48 | doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |