From: | "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com> |
---|---|
To: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Table refer leak in logical replication |
Date: | 2021-04-06 01:04:51 |
Message-ID: | OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I met a problem about trigger in logical replication.
I created a trigger after inserting data at subscriber, but there is a warning in the log of subscriber when the trigger fired:
WARNING: relcache reference leak: relation "xxx" not closed.
Example of the procedure:
------publisher------
create table test (a int primary key);
create publication pub for table test;
------subscriber------
create table test (a int primary key);
create subscription sub connection 'dbname=postgres' publication pub;
create function funcA() returns trigger as $$ begin return null; end; $$ language plpgsql;
create trigger my_trig after insert or update or delete on test for each row execute procedure funcA();
alter table test enable replica trigger my_trig;
------publisher------
insert into test values (6);
It seems an issue about reference leak. Anyone can fix this?
Regards,
Tang
From | Date | Subject | |
---|---|---|---|
Next Message | houzj.fnst@fujitsu.com | 2021-04-06 01:15:33 | RE: Table refer leak in logical replication |
Previous Message | Fujii Masao | 2021-04-06 00:41:21 | Re: Stronger safeguard for archive recovery not to miss data |