From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: houzj.fnst@fujitsu.com, Rahila Syed <rahilasyed90@gmail.com>
Cc: Peter Smith <smithpb2250@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Column Filtering in Logical Replication
Date: Wed, 12 Jan 2022 15:57:12 -0300
Message-ID: <202201121857.3dtj6tpe2fc7@alvherre.pgsql> (raw)
In-Reply-To: <20220111211053.GB14051@telsasoft.com>
On 2022-Jan-11, Justin Pryzby wrote:
> Is there any coordination between the "column filter" patch and the "row
> filter" patch ?
Not beyond the grammar, which I tested.
> Are they both on track for PG15 ?
I think they're both on track, yes.
> Has anybody run them together ?
Not me.
> I have a suggestion: for the functions for which both patches are adding
> additional argument types, define a filtering structure for both patches to
> use. Similar to what we did for some utility statements in a3dc92600.
>
> I'm referring to:
> logicalrep_write_update()
> logicalrep_write_tuple()
Fixed: the row filter patch no longer adds extra arguments to those
functions.
--
Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/
"Tiene valor aquel que admite que es un cobarde" (Fernandel)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, pryzby@telsasoft.com, peter.eisentraut@enterprisedb.com, tomas.vondra@enterprisedb.com, amit.kapila16@gmail.com, rahilasyed90@gmail.com, smithpb2250@gmail.com
Subject: Re: Column Filtering in Logical Replication
In-Reply-To: <202201121857.3dtj6tpe2fc7@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox