>> ...
>> Would that prevent VACUUM from doing its work? It should be able to
>> check the last startup xid to check that isn't the case, but suppose a
>> backend had exited without taking down the postmaster.
There is no such thing as a backend crashing without the postmaster
noticing (at least not unless your kernel is seriously broken).
It is entirely possible for a backend not to log xact commit or abort,
though --- in fact I think that is the normal case for a read-only
transaction (no point in writing a clog entry if no one will ever
consult it, eh?). This is not unsafe because the actual logic for
such things is:
1. Transaction still running? (check shared memory PGPROC array to
see if any backend claims to be running it)
2. Transaction committed or aborted according to pg_clog?
3. If none of the above, it must have crashed --- mark it aborted in
pg_clog.
Also, VACUUM's pruning logic does not depend at all on whether individual
transactions are still running or not. The issue there is the oldest
xid that is still shown as running in the shared-memory PGPROC array.
AFAIK this is highly reliable.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
