| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(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-06-27 01:06:25 |
| Message-ID: | CAHut+Ps8+w=sMFN3DdogREyeZO4ouJfwMSJoJtgNTkLdU9HATQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 26, 2023 at 11:44 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
...
> BTW, I have doubt that the restriction is not related with your commit.
> In other words, if the table has attributes which the datatype is not for operator
> class of Btree, we could not use REPLICA IDENTITY FULL. IIUC it is not documented.
> Please see attched script to reproduce that. The final DELETE statement cannot be
> replicated at the subscriber on my env.
>
Missing attachment?
------
Kind Regards,
Peter Smith.
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-06-27 01:09:42 | RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL |
| Previous Message | Peter Smith | 2023-06-27 01:02:06 | Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL |