Re: FailedAssertion at ReorderBufferCheckMemoryLimit()

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FailedAssertion at ReorderBufferCheckMemoryLimit()
Date: 2020-06-10 03:45:40
Message-ID: 3165bf70-401d-4c0b-3aca-8c6af73ba854@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/06/10 12:00, Amit Kapila wrote:
> 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?

Thanks for the patch! The patch looks good to me.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-06-10 03:50:21 Re: Resetting spilled txn statistics in pg_stat_replication
Previous Message Michael Paquier 2020-06-10 03:35:49 Re: Read access for pg_monitor to pg_replication_origin_status view