Hi
Testing on my home system, looking good... will try on my office system Mon=
day.
Note:
I am assuming that the uuid will mostly be used as a primary key on=
records that will exist in replicated databases to guarantee uniqueness. T=
he problem that is see with the current uuid functions for this purpose is =
that the generated uuid is very random causing great performance issues wit=
h the index; at least when using oracle and ms sql server, did not try with=
postgres, but must be similar. Usually inserting random data into an index=
of any kind is a worst case stress test. Hence the older style of uuid, ba=
sed on mac addresses and time tend to generate more sequential uuid's, at l=
east when inserting a bunch of records at once.
In other words it would be nice to have the old fashioned style of uuid's.
Regards
Eric
-----Original Message-----
From: Hiroshi Saito [mailto:z-saito@guitar.ocn.ne.jp]
Sent: Saturday, August 23, 2008 8:26 AM
To: Eric P. Melbardis; Bruce Momjian
Cc: Nicolas ANTONINI; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4274: uuid returns duplicate values
Hi Eric-san.
Done! please check it.
http://winpg.jp/~saito/pg_work/OSSP_win32/pg8.3.3-win-bin-uuid-ossp-2008082=
4.zip
I checked by the following machine.
-- Disktop(Windows-XP SP2)
Pentium(R) 4 CPU 2.6GHz
Memory 2GB
-- Notebook(Windows-XP SP2)
Pentium III CPU 495 MHz
Memory 256MB
--
Thanks.
Regards,
Hiroshi Saito
----- Original Message -----
From: "Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>
> Ooops, Please wait for this.
>
>> Please try this.(The date of a binary is 7/8)
>> http://winpg.jp/~saito/pg_work/OSSP_win32/pg8.3.3-win-bin-uuid-ossp-2008=
0823.zip
>> I will arrange thoroughly again.
>
> Anyhow, I have only now stale development environment.
> The time of a check is still required. thanks.
>
> Regards,
> Hiroshi Saito
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs