> > I think this argument is largely a red herring ... but if it makes you > > feel better, we could change the contents of the commit timestamp to > > be gettimeofday() output (seconds+microseconds) instead of just time() > > output. That should be precise enough for practical purposes. > > I am saying timestamp as used for specifying a recovery location might > not be unique enough, no?
Maybe the api should allow a xid only in addition to a timestamp, for use when timestamp alone is not precise enough. That would solve the problem of not finding the xid. I would stay away from microseconds. Andreas ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
