Re: Pg and compress - Mailing list pgsql-general

From John R Pierce
Subject Re: Pg and compress
Date
Msg-id 4E812244.4050209@hogranch.com
Whole thread Raw
In response to Re: Pg and compress  (Jov <zhao6014@gmail.com>)
List pgsql-general
On 09/26/11 5:53 PM, Jov wrote:
>
> Most are bigint and one field is varchar.
> There is no index.
>
>


well, scalar bigint values will be 8 bytes, plus a bit or 2 of overhead
per field. each complete tuple has a dozen bytes of header overhead.
tuples are stored as many as fit in a 8K block, unless you've specified
a fillfactor, whereupon that % of space is left free in each block.

if your CSV has mostly small integer values that are just 1-2-3 digits,
yeah, bigint will take more space than ascii.


--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast


pgsql-general by date:

Previous
From: Jov
Date:
Subject: Re: Pg and compress
Next
From: Andy Chambers
Date:
Subject: Re: Batching up data into groups of n rows