Postgres Pro
Downloads
Home   >   mailing lists

Re: Size comparison between a Composite type and an - Mailing list pgsql-general

From Douglas McNaught
Subject Re: Size comparison between a Composite type and an
Date
Msg-id 877j7fnppm.fsf@suzuka.mcnaught.org
Whole thread Raw
In response to Re: Size comparison between a Composite type and an  (Denis Gasparin <denis@edistar.com>)
Responses Re: Size comparison between a Composite type and an  (denis@edistar.com)
List pgsql-general
Tree view 
Denis Gasparin <denis@edistar.com> writes:

> If the composite data type has 4 bytes overhead, I save 4 bytes for
> each number... that is important because I must store many many
> numbers.

Yes, if size is a big issue you might be better off with a specialized
type.

-Doug

pgsql-general by date:

Previous
From: Denis Gasparin
Date:
Subject: Re: Size comparison between a Composite type and an
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Size comparison between a Composite type and an