]> granicus.if.org Git - postgresql/commit
Promote the assertion that XLogBeginInsert() is not called twice into ERROR.
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Sun, 28 Jun 2015 19:25:55 +0000 (22:25 +0300)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Sun, 28 Jun 2015 19:30:39 +0000 (22:30 +0300)
commita32c3ec893cafbd3a4b42c34270a80198f28f123
tree2a3b1a51b3cdb338cc9ca85cf00fef5660152251
parenta45c70acf35e43257d86313dcbb7bb0e5201fab1
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.
src/backend/access/transam/xloginsert.c