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. 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.
And for people that want char(1), they should be using "char", which
really is one byte (ex padding ofcourse).
Have a nice day,
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2006-06-29 15:27:07|
|Subject: Re: vacuum, performance, and MVCC|
|Previous:||From: Hiroshi Saito||Date: 2006-06-29 14:52:46|
|Subject: Re: Compilatiuon of source code for windows|
pgsql-general by date
|Next:||From: Jasbinder Bali||Date: 2006-06-29 15:24:35|
|Subject: Database connectivity using a unix shell|
|Previous:||From: Tino Wildenhain||Date: 2006-06-29 14:36:12|
|Subject: Re: Script for reading flat file without delimiters|