Re: Drawbacks of using BYTEA for PK? - Mailing list pgsql-general

From Chris Travers
Subject Re: Drawbacks of using BYTEA for PK?
Date
Msg-id 015601c3d9b1$348e36c0$54285e3d@winxp
Whole thread Raw
In response to Drawbacks of using BYTEA for PK?  (David Garamond <lists@zara.6.isreserved.com>)
Responses Re: Drawbacks of using BYTEA for PK?
List pgsql-general
----- Original Message -----
From: "Alex Satrapa" <alex@lintelsys.com.au>
> As long as you don't use RFC1918 addresses, the IPv4 address(es) of the
> host should be unique for the Internet. Append/prepend a 32 bit
> timestamp and you have a 64bit unique identifier that is "universally"
> unique (to one second).

Aarrgh...  So if you have 2 inserts in the same second, you have key
collision?  Why not append a sequence to that so you have:  Unique address
|| timestamp || sequence value.  In a case such as this I can see why you
might want to use md5() to hash that value.

Best Wishes,
Chris Travers


pgsql-general by date:

Previous
From: Anton.Nikiforov@loteco.ru
Date:
Subject: Re: Hierarchical queries
Next
From: "Chris Travers"
Date:
Subject: Re: Drawbacks of using BYTEA for PK?