Martijn van Oosterhout wrote:
On Thu, Jun 29, 2006 at 03:54:36PM +0200, Thomas Hallgren wrote:
I have to concur with this. Assume you use a bytea for a UUID that in
turn is used as a primary key. The extra overhead will be reflected in
all indexes, all foreign keys, etc. In a normalized database some tables
may consist of UUID columns only.
So you create a UUID type. It's cheap enough to create new types after
all, that's one of postgresql's strengths.
It would be a whole lot easier if I could use a domain.
What I'm saying is that it's
easier to create new fixed length types for the cases that need it,
than it is to redo the entire type handling of the backend.
Of course. But it's a matter of who does what. Your reasoning push the
burden to the users.
Regards,
Thomas Hallgren
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
