RE: row filtering for logical replication
Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Release cache tuple when no longer needed
- ed0fbc8e5ac9 15.0 landed
-
Add some additional tests for row filters in logical replication.
- ceb57afd3ce1 15.0 landed
-
Fix one of the tests introduced in commit 52e4f0cd47.
- cfb4e209ec15 15.0 landed
-
Allow specifying row filters for logical replication of tables.
- 52e4f0cd472d 15.0 landed
-
Move scanint8() to numutils.c
- cfc7191dfea3 15.0 cited
-
Replace Test::More plans with done_testing
- 549ec201d613 15.0 cited
-
Reduce relcache access in WAL sender streaming logical changes
- 6ce16088bfed 15.0 cited
-
Small cleanups related to PUBLICATION framework code
- c9105dd3660f 15.0 cited
-
Add a view to show the stats of subscription workers.
- 8d74fc96db5f 15.0 cited
-
Allow publishing the tables of schema.
- 5a2832465fd8 15.0 cited
-
Doc: improve documentation of CREATE/ALTER SUBSCRIPTION.
- 1882d6cca161 15.0 cited
-
Add PublicationTable and PublicationRelInfo structs
- 0c6828fa987b 15.0 cited
-
Remove unused argument "txn" in maybe_send_schema().
- 93d573d86571 15.0 cited
-
Add prepare API support for streaming transactions in logical replication.
- 63cf61cdeb7b 15.0 cited
-
Unify PostgresNode's new() and get_new_node() methods
- 201a76183e20 15.0 cited
-
Use l*_node() family of functions where appropriate
- 2b00db4fb0c7 15.0 cited
-
Add support for prepared transactions to built-in logical replication.
- a8fd13cab0ba 15.0 cited
-
Restore the portal-level snapshot after procedure COMMIT/ROLLBACK.
- ef9480509622 11.13 cited
-
Rename a parse node to be more general
- 91d1f2d30210 14.0 landed
-
Remove unused column atttypmod from initial tablesync query
- 4ad31bb2ef25 14.0 landed
-
SEARCH and CYCLE clauses
- 3696a600e229 14.0 cited
Attachments
- v45-0005-Cache-ExprState-per-pubaction.patch (application/octet-stream) patch v45-0005
- v45-0001-Row-filter-for-logical-replication.patch (application/octet-stream) patch v45-0001
- v45-0002-PS-Row-filter-validation-walker.patch (application/octet-stream) patch v45-0002
- v45-0003-Support-updates-based-on-old-and-new-tuple-in-ro.patch (application/octet-stream) patch v45-0003
- v45-0004-Tab-auto-complete-and-pgdump-support-for-Row-Fil.patch (application/octet-stream) patch v45-0004
- v45-0006-do-replica-identity-validation-when-UPDATE-or-DELETE.patch (application/octet-stream) patch v45-0006
On Wed, Dec 8, 2021 7:52 PM Ajin Cherian <itsajin@gmail.com> wrote: > On Tue, Dec 7, 2021 at 5:36 PM Peter Smith <smithpb2250@gmail.com> wrote: > > > > We were mid-way putting together the next v45* when your latest > > attachment was posted over the weekend. So we will proceed with our > > original plan to post our v45* (tomorrow). > > > > After v45* is posted we will pause to find what are all the > > differences between your unified patch and our v45* patch set. Our > > intention is to integrate as many improvements as possible from your > > changes into the v46* etc that will follow tomorrow’s v45*. On some > > points, we will most likely need further discussion. > > > Posting an update for review comments, using contributions majorly from > Peter Smith. > I've also included changes based on Euler's combined patch, specially changes > to documentation and test cases. > I have left out Hou-san's 0005, in this patch-set. Hou-san will provide a rebased > update based on this. Attach the Top up patch(as 0006) which do the replica identity validation when actual UPDATE/DELETE happen. I adjusted the patch name to make the change clearer. The new version top up patch addressed all comments from Peter[1] and Greg[2]. I also fixed a validation issue of the top up patch reported by Tang. The fix is: If we add a partitioned table with filter and pubviaroot is true, we need to validate the parent table's row filter when UPDATE the child table and we should convert the parent table's column to the child's during validation in case the column order of parent table is different from the child table. [1] https://www.postgresql.org/message-id/CAHut%2BPuBdXGLw1%2BCBoNxXUp3bHcHcKYWHx1RSGF6tY5aSLu5ZA%40mail.gmail.com [2] https://www.postgresql.org/message-id/CAJcOf-dgxGmRs54nxQSZWDc0gaHZWFf3n%2BBhOChNXhi_cb8g9A%40mail.gmail.com Best regards, Hou zj