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, Nov 18, 2021 at 4:32 PM Peter Smith <smithpb2250@gmail.com> wrote: > > On Mon, Nov 15, 2021 at 9:31 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Wed, Nov 10, 2021 at 12:36 PM Peter Smith <smithpb2250@gmail.com> wrote: > > > > > > On Mon, Nov 8, 2021 at 5:53 PM houzj.fnst@fujitsu.com > > > <houzj.fnst@fujitsu.com> wrote: > > > > > > > > 3) v37-0005 > > > > > > > > - no parse nodes of any kind other than Var, OpExpr, Const, BoolExpr, FuncExpr > > > > > > > > I think there could be other node type which can also be considered as simple > > > > expression, for exmaple T_NullIfExpr. > > > > > > The current walker restrictions are from a previously agreed decision > > > by Amit/Tomas [1] and from an earlier suggestion from Andres [2] to > > > keep everything very simple for a first version. > > > > > > Yes, you are right, there might be some additional node types that > > > might be fine, but at this time I don't want to add anything different > > > without getting their approval to do so. Anyway, additions like this > > > are all candidates for a future version of this row-filter feature. > > > > > > > I think we can consider T_NullIfExpr unless you see any problem with the same. > > Added in v40 [1] > I've noticed that row-filters that are testing NULL cannot pass the current expression validation restrictions. e.g.1 test_pub=# create publication ptest for table t1 where (a is null); ERROR: invalid publication WHERE expression for relation "t1" HINT: only simple expressions using columns, constants and immutable system functions are allowed e.g.2 test_pub=# create publication ptest for table t1 where (a is not null); ERROR: invalid publication WHERE expression for relation "t1" HINT: only simple expressions using columns, constants and immutable system functions are allowed So I think it would be useful to permit the NullTest also. Is it OK? ------ KInd Regards, Peter Smith. Fujitsu Australia