| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(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 16:48:23 |
| Message-ID: | 1169743703.5447.33.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Sun, 2007-01-21 at 00:17 +0100, Gevik Babakhani wrote:
> So.. do we agree for uuid to be included in the core?
I'd be curious to know the degree to which the proposed patch is
consistent with RFC 4122, which AFAIK is the most recent relevant
standard.
With regard to functions for generating UUIDs, I think we should at
least include the methods specified by RFC 4122 that can be implemented
without too many unportable assumptions. I believe that means MD5 & SHA1
hashing of an arbitrary identifier, and UUIDs generated via a PSRNG.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2007-01-25 16:49:12 | Re: tsearch in core patch, for inclusion |
| Previous Message | Nikolay Samokhvalov | 2007-01-25 16:35:25 | Re: tsearch in core patch, for inclusion |