Skip site navigation (1) Skip section navigation (2)

BUG #4586: Supporting of Binary instead Bytea for Primary Keys

From: "Miroslav Nachev" <miro(at)space-comm(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4586: Supporting of Binary instead Bytea for Primary Keys
Date: 2008-12-17 07:30:18
Message-ID: 200812170730.mBH7UIi2017445@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      4586
Logged by:          Miroslav Nachev
Email address:      miro(at)space-comm(dot)com
PostgreSQL version: 8.3
Operating system:   Windows
Description:        Supporting of Binary instead Bytea for Primary Keys
Details: 

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.

Responses

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2008-12-17 08:17:41
Subject: Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys
Previous:From: Tom LaneDate: 2008-12-17 00:55:31
Subject: Re: BUG #4582: Renaming sequences and default value

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group