Re: GUID for postgreSQL

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: John DeSoi <desoi(at)pgedit(dot)com>
Cc: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Tino Wildenhain <tino(at)wildenhain(dot)de>, Riaan van der Westhuizen <riaan(at)huizensoft(dot)co(dot)za>, Postgresql-General <pgsql-general(at)postgresql(dot)org>
Subject: Re: GUID for postgreSQL
Date: 2005-07-28 19:21:39
Message-ID: 20050728192139.GA29472@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 27, 2005 at 16:57:21 -0400,
John DeSoi <desoi(at)pgedit(dot)com> wrote:
>
> On Jul 27, 2005, at 4:46 PM, Scott Marlowe wrote:
>
> >So, how can two databases, not currently talking to one another,
> >guarantee that their GUIDs don't collide? using a large randomly
> >generated name space only reduces the chances of collision, it doesn't
> >actually guarantee it.
>
>
> Like MD5, there is no 100% guarantee, but the collision possibility
> supposed to be is very close to zero.

If you use a large enough space for the number you can reduce that
probability of an accidental collision to much less than that of
catastrophic hardware failure at which point it isn't noticably better
than having no chance of collisions.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Phil Endecott 2005-07-28 19:31:21 Re: Megabytes of stats saved after every connection
Previous Message Greg Stark 2005-07-28 19:12:33 Re: Megabytes of stats saved after every connection