Fix incorrect PITR message for transaction ROLLBACK PREPARED

Reaching PITR on such a transaction would cause the generation of a LOG
message mentioning a transaction committed, not aborted.

Oversight in 4f1b890.

Author: Simon Riggs
Discussion: https://postgr.es/m/CANbhV-GJ6KijeCgdOrxqMCQ+C8QiK657EMhCy4csjrPcEUFv_Q@mail.gmail.com
Backpatch-through: 9.6

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 828564f2200f72a163fcdf32ca9faa14f0b9824e..2d6c5583e40944280fb6f239974d59e81a857af6 100644 (file)
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -5845,7 +5845,7 @@ recoveryStopsBefore(XLogReaderState *record)
                xl_xact_abort *xlrec = (xl_xact_abort *) XLogRecGetData(record);
                xl_xact_parsed_abort parsed;
 
-               isCommit = true;
+               isCommit = false;
                ParseAbortRecord(XLogRecGetInfo(record),
                                                 xlrec,
                                                 &parsed);