From: Horst Herb <hherb@malleenet.net.au>
To: pgsql-sql@postgresql.org
Subject: Re: GUID in postgres
Date: Thu, 25 Oct 2001 13:53:27 +1000
Message-ID: <20011025034926.30847.qmail@gnumed.dhs.org> (raw)
In-Reply-To: <87adyhx7ew.fsf@toncho.dhh.gt.org>
References: <web-491315@davinci.ethosmedia.com>
<87adyhx7ew.fsf@toncho.dhh.gt.org>
On Thursday 25 October 2001 03:41, John Hasler wrote:
> Josh writes:
> > I'm sure you could make your own GUID, whatever one is.
>
> Globally Unique IDentifier, probably. Just hash a 128 bit random number
> with the current date.
That gives you no gurantee it will be unique.
What we are using is the following:
- All tables in need of a global ID _within_ a database inherit a globid
table which contains nothing but an ID of type serial.
- When we need cross-database unique IDs within the same system, the globid
table contains a database identifier as well (like the OID of the pg_database
entry for the database).
Horst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: hherb@malleenet.net.au
Subject: Re: GUID in postgres
In-Reply-To: <20011025034926.30847.qmail@gnumed.dhs.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox