From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | explaining the pg_total_relation_size/pg_relation_size results |
Date: | 2018-06-20 22:26:07 |
Message-ID: | CAOC+FBWk93oR6qj-iqi1EyZdzNGUQ=Vyxdz9ttGs0r=R1kYGMA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I have the follwing in a view to glance at the size of my relations:
pg_size_pretty(pg_relation_size(c.oid::regclass)) AS size,
pg_total_relation_size(c.oid::regclass) AS bytes
This view sorts by pg_relation_size(c.oid::regclass) descending.
The question is: the byte values are often higher for relations with a
lower size indicated by size. As I sit here, I see an 11GB table
of 23821893632 bytes and a 12GB table of 14545387520 bytes, and
lastly/weirdly, a 3194MB table of 19924844544 bytes.
Can someone give me the quck explainer here of what I am looking at? I tend
to trust the size more than the bytes but I want to understand both better.
Thanks.
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-06-20 22:42:03 | Re: explaining the pg_total_relation_size/pg_relation_size results |
Previous Message | Enrico Thierbach | 2018-06-20 19:04:02 | Re: Trouble matching a nested value in JSONB entries |