Re: XLog: how to log?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: XLog: how to log?
Date: 2004-05-11 22:09:51
Message-ID: 200405112209.i4BM9po09799@candle.pha.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> 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
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-05-11 22:13:27 Re: Probably security hole in postgresql-7.4.1
Previous Message Simon Riggs 2004-05-11 22:07:47 Re: XLog: how to log?