Re: row filtering for logical replication
Peter Smith <smithpb2250@gmail.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
On Thu, Dec 2, 2021 at 7:40 PM vignesh C <vignesh21@gmail.com> wrote: > ... > Thanks for the updated patch, few comments: > 1) Both testpub5a and testpub5c publication are same, one of them can be removed > +SET client_min_messages = 'ERROR'; > +CREATE PUBLICATION testpub5a FOR TABLE testpub_rf_tbl1 WHERE (a > 1) > WITH (publish="insert"); > +CREATE PUBLICATION testpub5b FOR TABLE testpub_rf_tbl1; > +CREATE PUBLICATION testpub5c FOR TABLE testpub_rf_tbl1 WHERE (a > 3) > WITH (publish="insert"); > +RESET client_min_messages; > +\d+ testpub_rf_tbl1 > +DROP PUBLICATION testpub5a, testpub5b, testpub5c; > > testpub5b will be covered in the earlier existing case above: > ALTER PUBLICATION testpib_ins_trunct ADD TABLE pub_test.testpub_nopk, > testpub_tbl1; > > \d+ pub_test.testpub_nopk > \d+ testpub_tbl1 > > I felt test related to testpub5b is also not required Skipped. Strictly speaking you may be correct to say this code path is already tested elsewhere. But this test case was meant for \d+ so I wanted it to be "self-contained" and easy to observe it displaying both with and without a filters both at the same time. > 3) testpub7 can be renamed to testpub6 to maintain the continuity > since the previous testpub6 did not succeed: > +CREATE OPERATOR =#> (PROCEDURE = testpub_rf_func, LEFTARG = integer, > RIGHTARG = integer); > +CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl3 WHERE (e =#> 27); > +-- fail - WHERE not allowed in DROP > +ALTER PUBLICATION testpub5 DROP TABLE testpub_rf_tbl3 WHERE (e < 27); > +-- fail - cannot ALTER SET table which is a member of a pre-existing schema > +SET client_min_messages = 'ERROR'; > +CREATE PUBLICATION testpub7 FOR ALL TABLES IN SCHEMA testpub_rf_myschema1; > +ALTER PUBLICATION testpub7 SET ALL TABLES IN SCHEMA > testpub_rf_myschema1, TABLE testpub_rf_myschema1.testpub_rf_tb16; > +RESET client_min_messages; > Fixed in v48 [1] > 4) Did this test intend to include where clause in testpub_rf_tb16, if > so it can be added: > +-- fail - cannot ALTER SET table which is a member of a pre-existing schema > +SET client_min_messages = 'ERROR'; > +CREATE PUBLICATION testpub7 FOR ALL TABLES IN SCHEMA testpub_rf_myschema1; > +ALTER PUBLICATION testpub7 SET ALL TABLES IN SCHEMA > testpub_rf_myschema1, TABLE testpub_rf_myschema1.testpub_rf_tb16; > +RESET client_min_messages; > Fixed in v48 [1] ------ [1] https://www.postgresql.org/message-id/CAHut%2BPuHz1oFM7oaiHeqxMQqd0L70bV_hT7u_mDf3b8As5kwig%40mail.gmail.com Kind Regards, Peter Smith. Fujitsu Australia