Kless wrote:
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
------------
No it is not. It is stored as 16 binary bytes. As text it won't fit into
16 bytes.
but this it's very inefficient as you can read here [1].
What on earth makes you assume that MySQL performance characteristics
apply to PostgreSQL? If you want to show that our implementation is
inefficient, you need to produce PostgreSQL performance tests to
demonstrate it.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
