| From: | "David Parker" <dparker(at)tazznetworks(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | estimating table size |
| Date: | 2004-07-26 22:14:06 |
| Message-ID: | 120DB10316D2B946A3A1BEFB82324BB1859962@kodos.tazznetworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Given a table, foo, created in a database but not populated, is there a
procedure that will return an estimate of the size of a given tuple in
that table? It looks like pgstattuple reports on actual table pages; I'm
looking for something that reads the lengths of each row, and knows what
the storage overhead would be (extra 4 bytes for varchar, for instance).
Alternatively, is there documentation somewhere that can give me a good
rule of thumb for this? I can add up the lengths of the columns and make
my own judgements about averages for varchar columns. The "hidden"
storage overhead is what I'm wondering about, I guess.
Thanks.
- DAP
======================================================
David Parker Tazz Networks (401) 709-5130
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Shevchenko | 2004-07-26 22:29:11 | parsing binary varchar[]-s |
| Previous Message | Steve Crawford | 2004-07-26 21:54:31 | Re: vacuumdb hanging database cluster |