From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 17:43:09 |
Message-ID: | CAOC+FBUmpiQtmwn_WNyE-jCZ57h7OebqgBGtpLYFwqBCdkoSaQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks, that was it exactly. PGAdmin session opened for a week. Argh. Gotta
have some conversations with some folks.
Do you guys have any kind of regular monitoring in place to flag users who
don't politely close their connections?
On Mon, Aug 5, 2019 at 10:24 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> > As a follow up, n_dead_tup from pg_stat_sys_tables for this TOAST table
> is
> > 7447444, live tuples, 623982, and tup_del 20823469. vacuum_count is 0.
>
> > Why can't I free those rows up?
>
> Old open transaction somewhere (possibly a prepared transaction?).
> Or a replication slot that's holding back the xmin horizon due to
> not keeping up.
>
> regards, tom lane
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Avinash Kumar | 2019-08-05 17:48:28 | Re: Diagnosing a massive toast file |
Previous Message | Tom Lane | 2019-08-05 17:24:27 | Re: Diagnosing a massive toast file |