Re: Diagnosing a massive toast file
| От | Wells Oliver |
|---|---|
| Тема | Re: Diagnosing a massive toast file |
| Дата | |
| Msg-id | CAOC+FBUmpiQtmwn_WNyE-jCZ57h7OebqgBGtpLYFwqBCdkoSaQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Diagnosing a massive toast file (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Diagnosing a massive toast file
RE: Diagnosing a massive toast file |
| Список | 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@sss.pgh.pa.us> wrote:
Wells Oliver <wells.oliver@gmail.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.oliver@gmail.com
wells.oliver@gmail.com
В списке pgsql-admin по дате отправления: