Re: ctid access is slow - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: ctid access is slow
Date
Msg-id 20050824094012.GE2972@merkur.hilbert.loc
Whole thread Raw
In response to Re: ctid access is slow  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-general
On Tue, Aug 23, 2005 at 11:36:31PM -0500, Jim C. Nasby wrote:

> A better solution is to use a combination of a timestamp and a sequence.
> Why both? Because it's possible for the clock to be set back (though
> this is something best avoided), and a sequence will eventually roll
> over. It's impossible to have a collision in this scenario unless you
> roll the clock way back AND reset the sequence (assuming you're using an
> integer sequence).
Or else use XMIN.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

pgsql-general by date:

Previous
From: "Roger Hand"
Date:
Subject: Re: [OT?] ETL tools
Next
From: Sean Davis
Date:
Subject: Re: ERROR: database is being accessed by other users