From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Diagnosing a massive toast file |
Date: | 2019-08-05 16:37:17 |
Message-ID: | CAOC+FBX1arTzF+_hx2WMsnOoF95gnnMZtNNkPUG+OKAERpisJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Yeah, trying to figure out what actual table is clearly in need of a vacuum
b/c of the size of that toast table.
On Mon, Aug 5, 2019 at 9:36 AM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> On 8/5/19 11:32 AM, Wells Oliver wrote:
>
> Hi all, I have not seen this before, but one our toast tables has gotten
> to 15GB, the biggest table in the DB. I don't know why, is there some way I
> can diagnose what's causing this?
>
> I don't think I've ever seen a toast table even half of this size, so
> it's concerning.
>
>
> We've got *lots* of toast tables that big. Are you asking how to find
> the "human readable name" associated with the toast table?
>
> And have you vacuumed it lately?
>
> --
> Angular momentum makes the world go 'round.
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-08-05 16:49:01 | Re: Diagnosing a massive toast file |
Previous Message | Ron | 2019-08-05 16:36:27 | Re: Diagnosing a massive toast file |