From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Matteo Grolla <matteo.grolla@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Can't explain db size
Date: Sun, 20 Dec 2015 17:08:04 -0600
Message-ID: <567734D4.4070202@BlueTreble.com> (raw)
In-Reply-To: <CAEW0--jM75OZPE8U1t=wBt4UvOJUirexQ0Ao5vZz=3oFmUvRwA@mail.gmail.com>
References: <CAEW0--jM75OZPE8U1t=wBt4UvOJUirexQ0Ao5vZz=3oFmUvRwA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, matteo.grolla@gmail.com
Subject: Re: Can't explain db size
In-Reply-To: <567734D4.4070202@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox