Re: Huge memory consumption on partitioned table with FKs

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Keisuke Kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>, tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com>, tatsuhito(dot)kasahara(dot)rd(at)hco(dot)ntt(dot)co(dot)jp
Subject: Re: Huge memory consumption on partitioned table with FKs
Date: 2020-12-02 13:46:04
Message-ID: CANP8+jJam6AVLg7tojD0cBDPP3PANXokhpUopM2+wqbDWpjeyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 1 Dec 2020 at 00:03, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Muhammad Usama 2020-12-02 13:46:43 Re: A new function to wait for the backend exit after termination
Previous Message legrand legrand 2020-12-02 13:41:36 Re: pg_stat_statements oddity with track = all