Re: FailedAssertion at ReorderBufferCheckMemoryLimit()

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FailedAssertion at ReorderBufferCheckMemoryLimit()
Date: 2020-06-10 03:00:15
Message-ID: CAA4eK1JNeaE_rq36GJ6ZST-+xrv2dpw+6-B2n9sLnTwLu6g7Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 9, 2020 at 2:28 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Tue, Jun 9, 2020 at 1:56 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
> >
>
> > I wonder if we may
> > need to keep evicting the transactions until we don't exceed
> > memory limit.
> >
>
> Yes, that should be the right fix here.
>

Can you please check whether the attached patch fixes the problem for you?

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment Content-Type Size
fix_rb_mem_ovfl_1.patch application/octet-stream 2.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2020-06-10 03:03:49 Re: proposal: possibility to read dumped table's name from file
Previous Message Justin Pryzby 2020-06-10 02:15:44 Re: Default setting for enable_hashagg_disk