UUID - Data type inefficient

From: Kless <jonas(dot)esp(at)googlemail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: UUID - Data type inefficient
Date: 2008-07-10 14:37:13
Message-ID: 9304edd3-33bb-466b-86a7-71f62b6d9750@d45g2000hsc.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The new data type, UUID, is stored as a string -char(16)-:

------------
struct pg_uuid_t
{
unsigned char data[UUID_LEN];
};
#define UUID_LEN 16
------------

but this it's very inefficient as you can read here [1].

The ideal would be use bit(128), but today isn't possible. One
possible solution would be create a structure with 2 fields, each one
with bit(64).

[1] http://www.mysqlperformanceblog.com/2007/03/13/to-uuid-or-not-to-uuid/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Hodges 2008-07-10 14:44:20 Re: Follow-up on replication hooks for PostgreSQL
Previous Message Andrew Dunstan 2008-07-10 14:30:42 Re: Protocol 3, Execute, maxrows to return, impact?