Remove incorrect assertion in reorderbuffer.c.

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Subject: Remove incorrect assertion in reorderbuffer.c.
Date: 2020-12-03 12:04:27
Message-ID: CAA4eK1KoOH0byboyYY40NBcC7Fe812trwTa+WY3jQF7WQWZbQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

Attachment Content-Type Size
v1-0001-Remove-incorrect-assertion-in-reorderbuffer.c.patch application/octet-stream 2.6 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-12-03 12:09:32 Re: autovac issue with large number of tables
Previous Message Anastasia Lubennikova 2020-12-03 09:54:33 Re: Commitfest 2020-11 is closed