| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Pg and compress |
| Date: | 2011-09-27 01:09:24 |
| Message-ID: | 4E812244.4050209@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Chambers | 2011-09-27 03:55:09 | Re: Batching up data into groups of n rows |
| Previous Message | Jov | 2011-09-27 00:53:41 | Re: Pg and compress |