| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Miroslav Nachev <miro(at)space-comm(dot)com> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys |
| Date: | 2008-12-17 09:45:33 |
| Message-ID: | 4948CA3D.1030200@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Miroslav Nachev wrote:
> And how to specify that bytea MUST be exact 16 bytes?
Well, you could put a constraint on the column, or create a domain with
such a constraint. But if you're dealing with uuids, you really want to
use the UUID data type anyway.
> What about the speed
> because this is very important?
> 1st of all when the length is variable then the speed is low.
The overhead is small enough that you'd never notice.
> 2nd when the column is with bigger length which require pointer to the data
> instead data, then the speed will be extremely low.
Again you're just assuming some overhead that's completely insignificant
in the big scheme of things.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2008-12-17 19:32:31 | Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys |
| Previous Message | Miroslav Nachev | 2008-12-17 09:36:08 | Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys |