Horton

Re: Huge memory consumption on partitioned table with FKs

Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>

View thread View on postgr.es
From: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Amit Langote <amitlangote09@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, keisuke kuroda <keisuke.kuroda.3862@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, tatsuhito.kasahara.rd@hco.ntt.co.jp
Date: 2021-03-12T03:35:08Z
Lists: pgsql-hackers 
On 2021/03/12 2:44, Tom Lane wrote:
> I wrote:
>> Now, maybe it's a coincidence that husky failed on a
>> partitioned-foreign-key test right after this patch went in, but I bet
>> not.  Since husky runs CLOBBER_CACHE_ALWAYS, it looks to me like we've
>> overlooked some cache-reset scenario or other.
> 
> After reproducing it here, that *is* a coincidence.  I shall now go beat
> up on the correct blame-ee, instead.


I did "make installcheck-parallel" on 7bb97211a, just in case. It was successful. :-D

Regards,
Tatsuro Yamada

Commits

  1. Avoid creating duplicate cached plans for inherited FK constraints.