Hi
I think most of you are missing the point here.
GUIDs are unique and they are required for Enterprise development.
For those of you who have used multi master replication on Oracle or MS
SQL, you know that identity columns and sequences are problematic. The
only way to work with primary key columns in to seed the values of the
identity column or sequence differently for each of the servers in the
cluster, such that, a duplicate value would never occur. This is a very
sloppy approach to dealing with the problem as it requires a
considerable amount of maintenance; furthermore, anyone who takes this
approach shouldn't be working with computers.
In this type of environment you would use a GUID in place of an identity
column. Since the value is unique on the individual server and on the
cluster of servers (because the MAC addresses are different) you won't
be getting errors from non-unique values being inserted in the primary
key during the replication.
We've have one system that has been running MS SQL for over a year now
without any GUID errors. The largest table in the system has over 19
million records.
Do a search for "multi master replication" and you should pick up some
info on how to properly implement a GUID. The simplest approach is to
use some combination of a sequence and the MAC address.
> Hi,
> Is there any concept of sys_Guid in postgres.
> If yes what is that ??
> As i am using GUID in sql and oracle, then what is counterpart of this
in postgres. It is urgent.
>
> Thanks in advance
> Bye
> Dinesh Parikh
