Re: [PATCHES] Patch for UUID datatype (beta)

From: "Jim C(dot) Nasby" <jimn(at)enterprisedb(dot)com>
To: Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Cc: mark(at)mark(dot)mielke(dot)cc, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Subject: Re: [PATCHES] Patch for UUID datatype (beta)
Date: 2006-09-19 13:53:05
Message-ID: 20060919135305.GV47167@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Tue, Sep 19, 2006 at 03:35:55PM +0200, Gevik Babakhani wrote:
> > As others have mentioned, using MAC address doesn't remove the
> > possibility of a collision.
> >
> > Maybe a good compromise that would allow a generator function to go into
> > the backend would be to combine the current time with a random number.
> > That will ensure that you won't get a dupe, so long as your clock never
> > runs backwards.
>
> I think that is a reasonable solution. I just wonder if there is a cross
> platform way to get the MAC address for all OS we support.

Well... how much OS-specific code do you want? :)

Another (not as good) possibility would be to use the IP address (along
with time and a random number).
--
Jim Nasby jimn(at)enterprisedb(dot)com
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Cave-Ayland 2006-09-19 13:55:38 Re: -HEAD planner issue wrt hash_joins on dbt3 ?
Previous Message Jim C. Nasby 2006-09-19 13:51:40 Re: Release notes

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2006-09-19 14:09:59 Incrementally Updated Backup
Previous Message mark 2006-09-19 13:51:23 Re: [HACKERS] Patch for UUID datatype (beta)