Re: pg_toast growth out - PostgreSQL 9.2 - Mailing list pgsql-admin

From David G. Johnston
Subject Re: pg_toast growth out - PostgreSQL 9.2
Date
Msg-id CAKFQuwa+BXKB4ib=+WC0Cg8hHqkB8pWduz-nRFHRvn958M9Eew@mail.gmail.com
Whole thread Raw
In response to pg_toast growth out - PostgreSQL 9.2  ("drum.lucas@gmail.com" <drum.lucas@gmail.com>)
List pgsql-admin
On Wed, Mar 16, 2016 at 3:47 PM, drum.lucas@gmail.com <drum.lucas@gmail.com> wrote:

Hi all,

Trying to understand how can the pg_toast table be 90% of my entire DB?

It isn't "the", its "one of my".  "One of my pg_toast" tables consumes 90% of my entire DB".  Though its remotely possible you only have one it is not generally the case.
 
SELECT nspname || '.' || relname AS "relation",   pg_size_pretty(pg_relation_size(C.oid)) AS "size" FROM pg_class C LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) WHERE nspname NOT IN ('pg_catalog', 'information_schema') ORDER BY pg_relation_size(C.oid) DESC LIMIT 20;

Results:

pg_toast.pg_toast_7255249   1581 GB
public.ja_feedlog   81 GB

Total DB size: 1.7 TB

What's going on here?

 

Is there anything I can do to save up some disk space?

Not outside of radical changes to your architecture or deleting records - though possibly marginal improvements could be made dependent upon the type of data that is being "toasted".

David J.



pgsql-admin by date:

Previous
From: "drum.lucas@gmail.com"
Date:
Subject: pg_toast growth out - PostgreSQL 9.2
Next
From: Nagy László Zsolt
Date:
Subject: Re: How to setup a good collation?