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
On Tues, Jan 18, 2022 9:27 AM Peter Smith <smithpb2250@gmail.com> wrote: > Here are some review comments for v66-0001 (review of updates since > v65-0001) Thanks for the comments! > ~~~ > > 1. src/backend/catalog/pg_publication.c - GetTopMostAncestorInPublication > > @@ -276,17 +276,45 @@ GetPubPartitionOptionRelations(List *result, > PublicationPartOpt pub_partopt, } > > /* > + * Returns the relid of the topmost ancestor that is published via this > + * publication if any, otherwise return InvalidOid. > + */ > > Suggestion: > "otherwise return InvalidOid." --> "otherwise returns InvalidOid." > Changed. > > 2. src/backend/commands/publicationcmds.c - > contain_invalid_rfcolumn_walker > > @@ -235,6 +254,337 @@ CheckObjSchemaNotAlreadyInPublication(List > *rels, List *schemaidlist, > } > > /* > + * Returns true, if any of the columns used in the row filter WHERE > + clause are > + * not part of REPLICA IDENTITY, false, otherwise. > > Suggestion: > ", false, otherwise" --> ", otherwise returns false." > Changed. > > 3. src/backend/replication/logical/tablesync.c - fetch_remote_table_info > > + * We do need to copy the row even if it matches one of the > + publications, > + * so, we later combine all the quals with OR. > > Suggestion: > > BEFORE > * We do need to copy the row even if it matches one of the publications, > * so, we later combine all the quals with OR. > AFTER > * We need to copy the row even if it matches just one of the publications, > * so, we later combine all the quals with OR. > Changed. > > 4. src/backend/replication/pgoutput/pgoutput.c - > pgoutput_row_filter_exec_expr > > + ret = ExecEvalExprSwitchContext(state, econtext, &isnull); > + > + elog(DEBUG3, "row filter evaluates to %s (isnull: %s)", > + DatumGetBool(ret) ? "true" : "false", > + isnull ? "false" : "true"); > + > + if (isnull) > + return false; > + > + return DatumGetBool(ret); > > That change to the logging looks incorrect - the "(isnull: %s)" value is > backwards now. > > I guess maybe the intent was to change it something like below: > > elog(DEBUG3, "row filter evaluates to %s (isnull: %s)", isnull ? "false" : > DatumGetBool(ret) ? "true" : "false", isnull ? "true" : "false"); I misread the previous comments. I think the original log is correct and I have reverted this change. Best regards, Hou zj