| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Gevik Babakhani <pgdev(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [DOCS] uuid type not documented |
| Date: | 2007-04-10 21:25:05 |
| Message-ID: | 3597.1176240305@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Neil Conway <neilc(at)samurai(dot)com> writes:
> On Tue, 2007-04-10 at 18:28 +0200, Peter Eisentraut wrote:
>> The problem is that most of the standard methods are platform dependent, as
>> they require MAC addresses or a "good" random source, for instance.
> http://archives.postgresql.org/pgsql-patches/2007-01/msg00392.php
> ISTM random() or similar sources is a sufficient PSRNG for the purposes
> of UUID generation -- I can't see anything in the RFC that would
> contradict that.
Doesn't seem like quite enough bits of uniqueness.
We could improve matters by incorporating the database's
pg_control.system_identifier into the UUID, substituting for the MAC
address we don't have a good way to get. system_identifier is currently
determined by the system clock at initdb time (to gettimeofday
precision), so it would add at least some additional bits of
randomness...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roman Neuhauser | 2007-04-11 05:28:17 | Re: [DOCS] uuid type not documented |
| Previous Message | Florian G. Pflug | 2007-04-10 20:04:36 | Re: [DOCS] uuid type not documented |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-10 21:36:17 | Re: Anyone interested in improving postgresql scaling? |
| Previous Message | Maxime Henrion | 2007-04-10 21:20:27 | Re: Anyone interested in improving postgresql scaling? |