Postgres Pro
Downloads
Home   >   mailing lists

relcache reference leak with pglogical replication to insert-onlypartitioned table? - Mailing list pgsql-hackers

From Jeremy Finzel
Subject relcache reference leak with pglogical replication to insert-onlypartitioned table?
Date
Msg-id CAMa1XUg9ZeLEe7F=wFdLds0GZODz=swPC0Qr56DQxhTeK_UGPg@mail.gmail.com
Whole thread Raw
Responses Re: relcache reference leak with pglogical replication toinsert-only partitioned table?  (Michael Paquier <michael@paquier.xyz>)
Re: relcache reference leak with pglogical replication toinsert-only partitioned table?  ("craig.ringer" <craig.ringer@2ndquadrant.com>)
List pgsql-hackers
Tree view
I understand it's not fully supported to replicate to a differently partitioned setup on a subscriber with either pglogical or the native logical replication, however I also know that INSERT triggers can be fired in replication mode.  I have an insert-only OLTP table that I want partitioned only on the subscriber system.  I have this setup using the "old style" partitioning as it is a 9.6 system.

Provider is 9.6.6 pglogical 2.1.1
Subscriber is 9.6.10 pglogical 2.1.1

Everything appears good as far as the data.  It is partitioning correctly.  Queries on the data are planning correctly.  However, I am now getting these WARNING messages constantly.  How concerned should I be?  Is there a fix for this?  Any insight is much appreciated!

2019-01-27 03:12:34.150 GMT,,,135600,,5c4d1f44.211b0,6794,,2019-01-27 03:02:28 GMT,54/0,1057372660,WARNING,01000,"relcache reference leak: relation ""foo_pkey"" not closed",,,,,"apply COMMIT in commit before 14DB/34DB1B78, xid 1476598649 commited at 2019-01-26 21:12:34.071673-06 (action #10) from node replorigin 22",,,,"pglogical apply 16420:2094659706"

Thank you!
Jeremy

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Variable-length FunctionCallInfoData
Next
From: Andrew Dunstan
Date:
Subject: Re: Variable-length FunctionCallInfoData