Repair two problems with WAL logging of sequence nextvalI() ops, as
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 15 Mar 2002 19:20:47 +0000 (19:20 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 15 Mar 2002 19:20:47 +0000 (19:20 +0000)
commitdd82ac711465de84f64e2a217db924b6b4c60a85
tree16c1cacf29aeaaced96b97e3d80ed59f5a15ba76
parent71bc8ddb21afadf6ec134a9bd6f190226b3b3d85
Repair two problems with WAL logging of sequence nextvalI() ops, as
per recent pghackers discussion: force a new WAL record at first nextval
after a checkpoint, and ensure that xlog is flushed to disk if a nextval
record is the only thing emitted by a transaction.
src/backend/access/transam/xact.c
src/backend/access/transam/xlog.c
src/backend/bootstrap/bootstrap.c
src/backend/commands/sequence.c
src/backend/postmaster/postmaster.c
src/include/access/xlog.h