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
- v78-0001-Allow-specifying-row-filters-for-logical-replication.patch (application/octet-stream) patch v78-0001
On Sat, Feb 5, 2022 7:51 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Fri, Feb 4, 2022 at 2:58 PM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> > wrote: > > > > On Thursday, February 3, 2022 11:11 PM houzj.fnst@fujitsu.com > > <houzj.fnst@fujitsu.com> > > > > Since the v76-0000-clean-up-pgoutput-cache-invalidation.patch has been > > committed, attach a new version patch set to make the cfbot happy. > > Also addressed the above comments related to tab-complete in 0002 patch. > > > > I don't like some of the error message changes in this new version. For example: > > v75: > +CREATE FUNCTION testpub_rf_func1(integer, integer) RETURNS boolean AS > $$ SELECT hashint4($1) > $2 $$ LANGUAGE SQL; > +CREATE OPERATOR =#> (PROCEDURE = testpub_rf_func1, LEFTARG = integer, > RIGHTARG = integer); > +CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl3 WHERE (e =#> 27); > +ERROR: invalid publication WHERE expression for relation "testpub_rf_tbl3" > +DETAIL: User-defined operators are not allowed. > > v77 > +CREATE FUNCTION testpub_rf_func1(integer, integer) RETURNS boolean AS > $$ SELECT hashint4($1) > $2 $$ LANGUAGE SQL; > +CREATE OPERATOR =#> (PROCEDURE = testpub_rf_func1, LEFTARG = integer, > RIGHTARG = integer); > +CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl3 WHERE (e =#> 27); > +ERROR: invalid publication WHERE expression LINE 1: ...ICATION > +testpub6 FOR TABLE testpub_rf_tbl3 WHERE (e =#> 27); > + ^ > +DETAIL: User-defined or mutable functions are not allowed > > I think the detailed message by v75 "DETAIL: User-defined operators are not > allowed." will be easier for users to understand. I have made some code changes > and refactoring to make this behavior like previous without removing the > additional checks you have added in v77. I have made a few changes to > comments and error messages. Attached is a top-up patch on your v77 patch > series. I suggest we can combine the > 0001 and 0002 patches as well. Thanks for the comments. Your changes look good to me. Attach the V78 patch which addressed the above changes and merged 0001 and 0002. Best regards, Hou zj