Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys
Date
Msg-id 4948B5A5.7010309@enterprisedb.com
Whole thread Raw
In response to BUG #4586: Supporting of Binary instead Bytea for Primary Keys  ("Miroslav Nachev" <miro@space-comm.com>)
Responses Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys  ("Miroslav Nachev" <miro@space-comm.com>)
List pgsql-bugs
Miroslav Nachev wrote:
> Most of the popular databases (Oracle, MySQL, MS SQL, etc.) support binary
> column type which can be used as primary key. For example UUID algorithm
> need of exact 16 bytes and is very useful for Primary Key. Of course it can
> be presented with characters in Hex format but in that case this will take
> 32 bytes which is 2 times bigger.
> It will be very helpful if in PostgreSQL binary/varbinary type is supported
> and can be used for indexes and primary keys.

There's a built-in UUID datatype that you might be interested in. It's
16 bytes, fixed-length.

Also, what's wrong with bytea?

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "Miroslav Nachev"
Date:
Subject: BUG #4586: Supporting of Binary instead Bytea for Primary Keys
Next
From: Heikki Linnakangas
Date:
Subject: Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys