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 Tue, Apr 12, 2022 at 11:31 AM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote: > > On Tuesday, April 12, 2022 8:40 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > FYI, I was playing with row filters and partitions recently, and while doing > > something a bit unusual I received a cache leak warning. > > > > Below are the steps to reproduce it: > > > > > > test_pub=# CREATE TABLE parent(a int primary key) PARTITION BY RANGE(a); > > CREATE TABLE > > > > test_pub=# CREATE TABLE child PARTITION OF parent DEFAULT; CREATE TABLE > > > > test_pub=# CREATE PUBLICATION p4 FOR TABLE parent WHERE (a < 5), child > > WHERE (a >= 5) WITH (publish_via_partition_root=true); > > CREATE PUBLICATION > > > > test_pub=# ALTER PUBLICATION p4 SET TABLE parent, child WHERE (a >= 5); > > ALTER PUBLICATION > > > > test_pub=# ALTER PUBLICATION p4 SET (publish_via_partition_root = false); > > 2022-04-11 17:37:58.426 AEST [28152] WARNING: cache reference leak: > > cache pg_publication_rel (49), tuple 0/12 has count 1 > > WARNING: cache reference leak: cache pg_publication_rel (49), tuple > > 0/12 has count 1 > > ALTER PUBLICATION > > Thanks for reporting. > > I think the reason is that we didn't invoke ReleaseSysCache when rftuple is > valid and no filter exists. We need to release the tuple whenever the > rftuple is valid. Attach a patch which fix this. > Thanks! Your patch could be applied cleanly, and the reported problem now seems fixed. ------ Kind Regards, Peter Smith. Fujitsu Australia.