Promote the assertion that XLogBeginInsert() is not called twice into ERROR.
Heikki Linnakangas <heikki.linnakangas@iki.fi>
Promote the assertion that XLogBeginInsert() is not called twice into ERROR. Seems like cheap insurance for WAL bugs. A spurious call to XLogBeginInsert() in itself would be fairly harmless, but if there is any data registered and the insertion is not completed/cancelled properly, there is a risk that the data ends up in a wrong WAL record. Per Jeff Janes's suggestion.
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/transam/xloginsert.c | modified | +3 −1 |