| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Matteo Grolla <matteo(dot)grolla(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Can't explain db size |
| Date: | 2015-12-20 23:08:04 |
| Message-ID: | 567734D4.4070202@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 12/15/15 3:52 AM, Matteo Grolla wrote:
> 1) Can you explain me the big difference between the result in A for
> table alf_node_properties: 17GB and the result in B: ~6GB ?
11GB of indexes would explain it.
> 2) Can you explain me the difference between the result in B: ~6GB and
> the result in C, the sum of all column sizes, 3717MB ?
Probably per-page and per-tuple overhead.
What does SELECT reltuples, relpages FROM pg_class WHERE oid =
'public.alf_node_properties'::regclass show?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artem Tomyuk | 2015-12-22 07:59:27 | Connections "Startup" |
| Previous Message | Pavel Stehule | 2015-12-18 15:33:11 | Re: Estimation row error |