Re: row filtering for logical replication
Petr Jelinek <petr.jelinek@2ndquadrant.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 23/11/2018 17:39, David Fetter wrote: > On Fri, Nov 23, 2018 at 12:03:27AM +0100, Petr Jelinek wrote: >> On 01/11/2018 01:29, Euler Taveira wrote: >>> Em qua, 28 de fev de 2018 às 20:03, Euler Taveira >>> <euler@timbira.com.br> escreveu: >>>> The attached patches add support for filtering rows in the publisher. >>>> >>> I rebased the patch. I added row filtering for initial >>> synchronization, pg_dump support and psql support. 0001 removes unused >>> code. 0002 reduces memory use. 0003 passes only structure member that >>> is used in create_estate_for_relation. 0004 reuses a parser node for >>> row filtering. 0005 is the feature. 0006 prints WHERE expression in >>> psql. 0007 adds pg_dump support. 0008 is only for debug purposes (I'm >>> not sure some of these messages will be part of the final patch). >>> 0001, 0002, 0003 and 0008 are not mandatory for this feature. >> >> Hi, >> >> I think there are two main topics that still need to be discussed about >> this patch. >> >> Firstly, I am not sure if it's wise to allow UDFs in the filter clause >> for the table. The reason for that is that we can't record all necessary >> dependencies there because the functions are black box for parser. > > Some UDFs are not a black box for the parser, namely ones written in > SQL. Would it make sense at least not to foreclose the non-(black box) > option? > Yeah inlinable SQL functions should be fine, we just need the ability to extract dependencies. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services