Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Many transactions are going to have the same timestamp because that just
> > isn't precise enough to choose a particular transaction.
> 
> 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?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to