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: > ... > > 2) testpub5 and testpub_syntax2 are similar, one of them can be removed: > +SET client_min_messages = 'ERROR'; > +CREATE PUBLICATION testpub5 FOR TABLE testpub_rf_tbl1, > testpub_rf_tbl2 WHERE (c <> 'test' AND d < 5); > +RESET client_min_messages; > +\dRp+ testpub5 > > +SET client_min_messages = 'ERROR'; > +CREATE PUBLICATION testpub_syntax2 FOR TABLE testpub_rf_tbl1, > testpub_rf_myschema.testpub_rf_tbl5 WHERE (h < 999); > +RESET client_min_messages; > +\dRp+ testpub_syntax2 > +DROP PUBLICATION testpub_syntax2; > To re-confirm my original motivation for adding the syntax2 test I coded some temporary logging into the different PublicationObjSpec cases. After I re-ran the regression tests, here are some extracts from the postmaster.log: (for testpub5) 2022-01-14 13:06:32.149 AEDT client backend[21853] pg_regress/publication LOG: !!> TABLE relation_expr OptWhereClause 2022-01-14 13:06:32.149 AEDT client backend[21853] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub5 FOR TABLE testpub_rf_tbl1, testpub_rf_tbl2 WHERE (c <> 'test' AND d < 5) WITH (publish = 'insert'); 2022-01-14 13:06:32.149 AEDT client backend[21853] pg_regress/publication LOG: !!> ColId OptWhereClause 2022-01-14 13:06:32.149 AEDT client backend[21853] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub5 FOR TABLE testpub_rf_tbl1, testpub_rf_tbl2 WHERE (c <> 'test' AND d < 5) WITH (publish = 'insert'); (for syntax2) 2022-01-14 13:06:32.186 AEDT client backend[21853] pg_regress/publication LOG: !!> TABLE relation_expr OptWhereClause 2022-01-14 13:06:32.186 AEDT client backend[21853] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_syntax2 FOR TABLE testpub_rf_tbl1, testpub_rf_schema1.testpub_rf_tbl5 WHERE (h < 999) WITH (publish = 'insert'); 2022-01-14 13:06:32.186 AEDT client backend[21853] pg_regress/publication LOG: !!> ColId indirection OptWhereClause 2022-01-14 13:06:32.186 AEDT client backend[21853] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_syntax2 FOR TABLE testpub_rf_tbl1, testpub_rf_schema1.testpub_rf_tbl5 WHERE (h < 999) WITH (publish = 'insert'); From those logs you can see although the SQLs looked to be similar they actually take different PublicationObjSpec execution paths in the gram.y: i.e. " ColId OptWhereClause" Versus " ColId indirection OptWhereClause" ~~ So this review comment can be skipped. Both tests should be retained. ------ Kind Regards, Peter Smith. Fujitsu Australia