Re: Column Filtering in Logical Replication - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: Column Filtering in Logical Replication
Date
Msg-id 16e83ce3-8415-b732-37b2-c3329a2c13a1@enterprisedb.com
Whole thread Raw
In response to Re: Column Filtering in Logical Replication  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Column Filtering in Logical Replication  (Amit Kapila <amit.kapila16@gmail.com>)
RE: Column Filtering in Logical Replication  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
RE: Column Filtering in Logical Replication  ("shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>)
Re: Column Filtering in Logical Replication  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On 3/12/22 05:30, Amit Kapila wrote:
>> ...
> 
> Okay, please find attached. I have done basic testing of this, if we
> agree with this approach then this will require some more testing.
> 

Thanks, the proposed changes seem like a clear improvement, so I've
added them, with some minor tweaks (mostly to comments).

I've also included the memory context rename (entry_changes to the
change proposed by Wang Wei, using a single SQL command in tablesync.

And I've renamed the per-entry memory context to entry_cxt, and used it
for the column list.


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment

pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Issue with pg_stat_subscription_stats
Next
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON: JSON_TABLE