Repair two problems with WAL logging of sequence nextvalI() ops, as
Tom Lane <tgl@sss.pgh.pa.us>
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.
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/transam/xact.c | modified | +47 −29 |
| src/backend/access/transam/xlog.c | modified | +61 −25 |
| src/backend/bootstrap/bootstrap.c | modified | +2 −2 |
| src/backend/commands/sequence.c | modified | +29 −7 |
| src/backend/postmaster/postmaster.c | modified | +2 −2 |
| src/include/access/xlog.h | modified | +6 −3 |