Re: Drawbacks of using BYTEA for PK?

From: "Chris Travers" <chris(at)travelamericas(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Drawbacks of using BYTEA for PK?
Date: 2004-01-13 07:39:53
Message-ID: 015601c3d9b1$348e36c0$54285e3d@winxp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


----- Original Message -----
From: "Alex Satrapa" <alex(at)lintelsys(dot)com(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2004-01-13 07:54:41 Re: Drawbacks of using BYTEA for PK?
Previous Message Ben Marklein 2004-01-13 07:39:17 unique index creation failure in 7.4.1 - bug?