aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2015-06-28 22:25:55 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2015-06-28 22:30:39 +0300
commita32c3ec893cafbd3a4b42c34270a80198f28f123 (patch)
tree2a3b1a51b3cdb338cc9ca85cf00fef5660152251 /src/backend/access/transam/xlog.c
parenta45c70acf35e43257d86313dcbb7bb0e5201fab1 (diff)
downloadpostgresql-a32c3ec893cafbd3a4b42c34270a80198f28f123.tar.gz
postgresql-a32c3ec893cafbd3a4b42c34270a80198f28f123.zip
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.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions