Re: Huge memory consumption on partitioned table with FKs

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>, keisuke kuroda <keisuke(dot)kuroda(dot)3862(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: 2021-03-03 13:59:35
Message-ID: CA+HiwqH1JGGcR3erGxYwAocT_-Ys5_KDfdQEq8dZ+12nvNS8hw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi David,

On Wed, Mar 3, 2021 at 10:21 PM David Steele <david(at)pgmasters(dot)net> wrote:
> On 12/7/20 10:59 PM, Amit Langote wrote:
> > On Tue, Dec 8, 2020 at 12:04 PM Kyotaro Horiguchi
> > <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> >> At Tue, 8 Dec 2020 01:16:00 +0900, Amit Langote <amitlangote09(at)gmail(dot)com> wrote in
> >>> On Mon, Dec 7, 2020 at 23:48 Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >>>>
> >>>> I think this bit about splitting the struct is a distraction. Let's get
> >>>> a patch that solves the bug first, and then we can discuss what further
> >>>> refinements we want to do. I think we should get your patch in
> >>>> CA+HiwqEOrfN9b=f3sDmySPGc4gO-L_VMFHXLLxVmmdP34e64+w(at)mail(dot)gmail(dot)com
> >>>> committed (which I have not read yet.) Do you agree with this plan?
> >>>
> >>>
> >>> Yeah, I agree.
> >>
> >> Or https://www.postgresql.org/message-id/CA+HiwqGrr2YOO6voBM6m_OAc9w-WMxe1gOuQ-UyDPin6zJtyZw@mail.gmail.com ?
> >>
> >> +1 from me to either one.
> >
> > Oh, I hadn't actually checked the actual message that Alvaro
> > mentioned, but yeah I too am fine with either that one or the latest
> > one.
>
> Any progress on the decision of how to handle this bug? Not sure if that
> was handled elsewhere but it appears to be key to making progress on
> this patch.

The v3 patch posted on Dec 4 is still what is being proposed to fix this.

I don't know of any unaddressed comments on the patch, so I've marked
the entry Ready for Committer.

--
Amit Langote
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-03-03 14:07:21 Re: Parallel INSERT (INTO ... SELECT ...)
Previous Message Peter Eisentraut 2021-03-03 13:55:41 Re: OpenSSL 3.0.0 compatibility