| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nolan Cafferky <Nolan(dot)Cafferky(at)rbsinteractive(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Problems with VACUUM and "dead row versions cannot be removed yet" |
| Date: | 2006-10-18 17:59:59 |
| Message-ID: | 28531.1161194399@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Nolan Cafferky <Nolan(dot)Cafferky(at)rbsinteractive(dot)com> writes:
> I've got an admin_sessions table on a postgres 8.0.8 server that gets
> updated frequently, with about 30 live rows at any given time. We
> VACUUM the table nightly, which has served us with no problems for quite
> some time. Well, this morning we noticed some seriously slow queries
> against the table, and VACUUM VERBOSE reported around 84,000 rows that
> were "nonremovable". Same results with VACUUM FULL ANALYZE VERBOSE.
Lots of nonremovable rows means you've got some really old open
transactions. Look into pg_stat_activity or pg_locks to help find
the culprit.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-10-18 19:10:27 | Re: [PERFORM] autovacuum on a -mostly- r/o table |
| Previous Message | Nolan Cafferky | 2006-10-18 17:25:40 | Problems with VACUUM and "dead row versions cannot be removed yet" |