On Sat, 2009-12-05 at 22:56 +0200, Heikki Linnakangas wrote:
So that RecordKnownAssignedTransactionIds() call needs to be put back.
OK
BTW, if you want to resurrect the check in KnownAssignedXidsRemove(),
you also need to not complain before you reach the running-xacts record
and open up
On Fri, 2009-12-04 at 10:23 +0200, Heikki Linnakangas wrote:
@Heikki: Why is error checking in KnownAssignedXidsRemove() #ifdef'd
out??
It's explained in the comment:
/* XXX: This can still happen: If a transaction with a subtransaction
* that haven't been reported yet aborts, and no
Simon Riggs wrote:
On Fri, 2009-12-04 at 10:23 +0200, Heikki Linnakangas wrote:
@Heikki: Why is error checking in KnownAssignedXidsRemove() #ifdef'd
out??
It's explained in the comment:
/* XXX: This can still happen: If a transaction with a subtransaction
* that haven't been reported yet
There's a couple of items on the TODO page
(https://wiki.postgresql.org/wiki/Hot_Standby_TODO) that haven't been
discussed on-list:
In normal operation, a few commands call ForceSyncCommit() to force non-async
commit. Should ForceSyncCommit force an XLogFlush() during recovery as well?
