Re: Column Filtering in Logical Replication

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Column Filtering in Logical Replication
Date: 2021-12-28 21:04:27
Message-ID: 202112282104.jc4vhbgg3agi@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

OK, getting closer now. I've fixed the code to filter them column list
during the initial sync, and added some more tests for code that wasn't

There are still some XXX comments. The one that bothers me most is the
lack of an implementation that allows changing the column list in a
publication without having to remove the table from the publication

Álvaro Herrera 39°49'30"S 73°17'W —
"I'm always right, but sometimes I'm more right than other times."
(Linus Torvalds)

Attachment Content-Type Size
column-filtering-11.patch text/x-diff 62.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Moench-Tegeder 2021-12-28 21:38:12 Re: [PROPOSAL] Make PSQLVAR on \getenv opitional
Previous Message Andrew Dunstan 2021-12-28 20:45:40 Re: [PROPOSAL] Make PSQLVAR on \getenv opitional