RE: row filtering for logical replication - Mailing list pgsql-hackers

From houzj.fnst@fujitsu.com
Subject RE: row filtering for logical replication
Date
Msg-id TYAPR01MB57240C054D95F0AE55618D2C94439@TYAPR01MB5724.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: row filtering for logical replication  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
Responses RE: row filtering for logical replication
RE: row filtering for logical replication
Re: row filtering for logical replication
List pgsql-hackers
On Mon, Dec 27, 2021 9:19 PM Hou Zhijie <houzj.fnst@fujitsu.com> wrote:
> On Mon, Dec 27, 2021 9:16 PM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
> wrote:
> > On Thur, Dec 23, 2021 4:28 PM Peter Smith <smithpb2250@gmail.com> wrote:
> > > Here is the v54* patch set:
> >
> > Attach the v55 patch set which add the following testcases in 0002 patch.

When reviewing the row filter patch, I found few things that could be improved.
1) We could transform the same row filter expression twice when
   ALTER PUBLICATION ... SET TABLE WHERE (...). Because we invoke
   GetTransformedWhereClause in both AlterPublicationTables() and
   publication_add_relation(). I was thinking it might be better if we only
   transform the expression once in AlterPublicationTables().

2) When transforming the expression, we didn’t set the correct p_sourcetext.
   Since we need to transforming serval expressions which belong to different
   relations, I think it might be better to pass queryString down to the actual
   transform function and set p_sourcetext to the actual queryString.

Attach a top up patch 0004 which did the above changes.

Best regards,
Hou zj

Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: sequences vs. synchronous replication
Next
From: "Godfrin, Philippe E"
Date:
Subject: toast tables and toast indexes