pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Diagnosing a massive toast file
Date: Mon, 05 Aug 2019 12:49:01 -0400
Message-ID: <6018.1565023741@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOC+FBX1arTzF+_hx2WMsnOoF95gnnMZtNNkPUG+OKAERpisJg@mail.gmail.com>
References: <CAOC+FBUPopsKh5wV5VC-CHCnVirtTghhwNwEtSD2ZaCZbXwOFg@mail.gmail.com>
	<3da6ffe8-28ef-fb9a-e6e8-1f0d243cc8e9@gmail.com>
	<CAOC+FBX1arTzF+_hx2WMsnOoF95gnnMZtNNkPUG+OKAERpisJg@mail.gmail.com>

Wells Oliver <wells.oliver@gmail.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

view thread (12+ messages)  latest in thread

Message-ID: <6018.1565023741@sss.pgh.pa.us>
Permalink:  ../6018.1565023741@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6018.1565023741@sss.pgh.pa.us

copy link · copy postgr.es

reply

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, wells.oliver@gmail.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Diagnosing a massive toast file
  In-Reply-To: <6018.1565023741@sss.pgh.pa.us>

* 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