Horton

Re: Huge memory consumption on partitioned table with FKs

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndquadrant.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, Keisuke Kuroda <keisuke.kuroda.3862@gmail.com>, tatsuro.yamada.tf@nttcom.co.jp, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Amit Langote <amitlangote09@gmail.com>, tatsuhito.kasahara.rd@hco.ntt.co.jp
Date: 2020-12-02T13:46:04Z
Lists: pgsql-hackers 
On Tue, 1 Dec 2020 at 00:03, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> cache entry is reused in the common case where they are identical.

Does a similar situation exist for partition statistics accessed
during planning? Or planning itself?

It would be useful to avoid repeated access to similar statistics and
repeated planning of sub-plans for similar partitions.

-- 
Simon Riggs                http://www.EnterpriseDB.com/

Commits

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