Re: Diagnosing a massive toast file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Diagnosing a massive toast file
Date: 2019-08-05 16:49:01
Message-ID: 6018.1565023741@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> Yeah, trying to figure out what actual table is clearly in need of a vacuum
> b/c of the size of that toast table.

Something like

select relname from pg_class
where reltoastrelid = 'pg_toast.pg_toast_NNN'::regclass;

(or, if you have potential duplicate relnames, select oid::regclass ...)

The mere fact that it's big does not indicate a problem, though.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Wells Oliver 2019-08-05 17:00:58 Re: Diagnosing a massive toast file
Previous Message Wells Oliver 2019-08-05 16:37:17 Re: Diagnosing a massive toast file