From: | Jian Shi <jshi(at)unitrends(dot)com> |
---|---|
To: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | table size is bigger than expected |
Date: | 2011-08-04 18:56:56 |
Message-ID: | 68B6AA6E4AA4D840865FAB5BEC6707C108183089@UNIATLEX2010.unitrends.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hey,
I'm a new user of PostgreSQL. I found one of my tables is taking unexpectedly large space:
select pg_size_pretty(pg_relation_size('archive_files'));
pg_size_pretty
----------------
1113 MB
The structure of this table is like:
Column | Type | Modifiers
------------+-------------------+-----------
archive_id | integer | not null
dir_no | integer | not null
fname | character varying | not null
type | smallint | not null
size | bigint | not null
mod_date | integer | not null
blocks | bigint | not null
blk_offset | bigint | not null
the field "fname" stores file names without any directory names. In our case, each record is expected to take around 300 bytes.
However, this table contains 934829 records, which means each record takes about 1.2KB.
I did vaccum, reindex, the size is still the same. Is there anything else that I can do?
Thanks!
John
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pitts | 2011-08-04 20:17:30 | Re: table size is bigger than expected |
Previous Message | Robert Ayrapetyan | 2011-08-04 18:33:31 | Re: Performance die when COPYing to table with bigint PK |