| From: | "shiy(dot)fnst(at)fujitsu(dot)com" <shiy(dot)fnst(at)fujitsu(dot)com> |
|---|---|
| To: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com> |
| Subject: | RE: Table refer leak in logical replication |
| Date: | 2021-04-06 01:49:15 |
| Message-ID: | OSZPR01MB6310334183120AC95DECBB49FD769@OSZPR01MB6310.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> BTW, it seems better to add a testcase for this ?
I think the test for it can be added in src/test/subscription/t/003_constraints.pl, which is like what in my patch.
Regards,
Shi yu
| Attachment | Content-Type | Size |
|---|---|---|
| tests_for_table_refer_leak.diff | application/octet-stream | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | torikoshia | 2021-04-06 01:57:01 | Re: Get memory contexts of an arbitrary backend process |
| Previous Message | houzj.fnst@fujitsu.com | 2021-04-06 01:15:33 | RE: Table refer leak in logical replication |