Remove incorrect assertion in reorderbuffer.c.
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Dilip Kumar <dilipbalaut@gmail.com>
Date: 2020-12-03T12:04:27Z
Lists: pgsql-hackers
Attachments
- v1-0001-Remove-incorrect-assertion-in-reorderbuffer.c.patch (application/octet-stream) patch v1-0001
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?
Commits
-
Remove incorrect assertion in reorderbuffer.c.
- 8ae4ef4fb0e0 14.0 landed