| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org, Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
| Subject: | Re: guid/uuid datatype |
| Date: | 2007-01-20 16:30:35 |
| Message-ID: | 1169310635.27197.55.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Fri, 2007-01-19 at 23:00 -0500, Tom Lane wrote:
> Per previous discussion, the main problem with a uuid type is the
> new-uuid generator function, which tends to involve a bunch of
> not-so-portable assumptions and code.
RFC 4122 specifies several ways of generating UUIDs:
* via the computer's MAC address and the time since the Gregorian epoch
in nanoseconds
* via MD5 or SHA1 hashing of a given string of URL, or similar
identifier
* via a PSRNG
Only the first of these presents any portability concerns, AFAICS.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-01-20 17:02:36 | Re: [PATCHES] psql \lo_* quiet mode patch |
| Previous Message | Bruce Momjian | 2007-01-20 16:07:04 | Re: [PATCHES] Tablespace for temporary |