Ensure to send a prepare after we detect concurrent abort during decoding.
Amit Kapila <akapila@postgresql.org>
Ensure to send a prepare after we detect concurrent abort during decoding. It is possible that while decoding a prepared transaction, it gets aborted concurrently via a ROLLBACK PREPARED command. In that case, we were skipping all the changes and directly sending Rollback Prepared when we find the same in WAL. However, the downstream has no idea of the GID of such a transaction. So, ensure to send prepare even when a concurrent abort is detected. Author: Ajin Cherian Reviewed-by: Markus Wanner, Amit Kapila Discussion: https://postgr.es/m/f82133c6-6055-b400-7922-97dae9f2b50b@enterprisedb.com
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/logicaldecoding.sgml | modified | +9 −6 |
| src/backend/replication/logical/reorderbuffer.c | modified | +8 −0 |
Documentation touched
Discussion
- [PATCH] add concurrent_abort callback for output plugin 31 messages · 2021-03-25 → 2021-04-26