Re: Remove incorrect assertion in reorderbuffer.c. - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Remove incorrect assertion in reorderbuffer.c.
Date
Msg-id CAFiTN-sVnxGOwtXWkuYaB2JtfdHFV600HiVUOxOs=AQyXOiDxg@mail.gmail.com
Whole thread Raw
In response to Remove incorrect assertion in reorderbuffer.c.  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Remove incorrect assertion in reorderbuffer.c.
List pgsql-hackers
On Thu, Dec 3, 2020 at 5:33 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> We start recording changes in ReorderBufferTXN even before we reach
> SNAPBUILD_CONSISTENT state so that if the commit is encountered after
> reaching that we should be able to send the changes of the entire
> transaction. Now, while recording changes if the reorder buffer memory
> has exceeded logical_decoding_work_mem then we can start streaming if
> it is allowed and we haven't yet streamed that data. However, we must
> not allow streaming to start unless the snapshot has reached
> SNAPBUILD_CONSISTENT state.
>
> I have also improved the comments atop ReorderBufferResetTXN to
> mention the case when we need to continue streaming after getting an
> error.
>
> Attached patch for the above changes.
>
> Thoughts?

LGTM.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Huge memory consumption on partitioned table with FKs
Next
From: torikoshia
Date:
Subject: Re: Is it useful to record whether plans are generic or custom?