Skip site navigation (1) Skip section navigation (2)

Re: guid/uuid datatype

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Gevik Babakhani <pgdev(at)xs4all(dot)nl>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: guid/uuid datatype
Date: 2007-01-25 18:35:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
>> The MAC-based generator function could also be included in the backend,
>> actually: it just needs to take an argument of type "macaddr". It would
>> then be up to the user (and/or various pgfoundry and contrib/ modules)
>> to find a way to determine the local machine's MAC address, which
>> presumably can't be done reliably in a portable fashion.
> I assume we could just allow the MAC address or some unique idenfier to
> be specified in postgesql.conf. 

Well at that point why don't we allow it to be specified per database?

ALTER DATABASE foo SET uuid_salt =


That would be pretty cool, but I am sure most will shoot that down in
flames :)


Joshua D. Drake



      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997

Donate to the PostgreSQL Project:
PostgreSQL Replication:

In response to

pgsql-patches by date

Next:From: Gevik BabakhaniDate: 2007-01-25 19:25:14
Subject: Re: guid/uuid datatype
Previous:From: Bruce MomjianDate: 2007-01-25 18:26:50
Subject: Re: guid/uuid datatype

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group