From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | Greg Nancarrow <gregn4422(at)gmail(dot)com> |
Cc: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ajin Cherian <itsajin(at)gmail(dot)com>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com> |
Subject: | Re: Added schema level support for publication. |
Date: | 2021-07-12 09:23:53 |
Message-ID: | CALDaNm3tQuF4SDMkuSv0xJDRQAhQ5Ow_UT9if3BTE3ocnKQfDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 9, 2021 at 12:12 PM Greg Nancarrow <gregn4422(at)gmail(dot)com> wrote:
>
> On Fri, Jul 9, 2021 at 1:28 PM houzj(dot)fnst(at)fujitsu(dot)com
> <houzj(dot)fnst(at)fujitsu(dot)com> wrote:
> >
> > Currently, postgres caches publication actions info in the
> > RelationData::rd_pubactions, but after applying the patch, it seems
> > rd_pubactions is not initialized when using schema level publication.
> >
> > It cound result in some unexpected behaviour when checking if command
can be
> > executed with current replica identity.
> >
>
> While testing this patch, I'm finding that for a FOR SCHEMA
> publication, UPDATEs and DELETEs on tables belonging to that schema
> are not getting replicated (but INSERTs and TRUNCATEs are).
> Could this be related to the issues that Hou-san has identified?
Thanks for reporting this issue. I felt this issue is the same as the issue
which Hou San had reported. This issue is fixed in the v10 patch attached
at [1].
[1] -
https://www.postgresql.org/message-id/CALDaNm2%2BtR%2B8R-sD1CSyMbZcZbkintZE-avefjsp7LCkm6HMmw%40mail.gmail.com
Regards,
Vignesh
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2021-07-12 09:31:23 | Re: row filtering for logical replication |
Previous Message | vignesh C | 2021-07-12 09:20:38 | Re: Added schema level support for publication. |