| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike angelo <angelocmp(at)yahoo(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_toast |
| Date: | 2009-04-09 16:05:21 |
| Message-ID: | 16068.1239293121@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Mike angelo <angelocmp(at)yahoo(dot)com> writes:
> Reindexing produced no reduction in size of the table in question, and a VACUUM ANALYZE VERBOSE pg_toast_293523 produced the message:
> skipping "pg_toast_293523" --- cannot vacuum indexes, views, or special system tables.
Issue the vacuum against the owning table instead. (If you're not sure
which that is, joining pg_class.reltoastrelid to pg_class.oid will
help.)
In general it sounds like you need to crank up the aggressiveness of
autovacuum, and perhaps look at whether your application is doing
useless updates on very wide fields.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Péter Kovács | 2009-04-09 21:48:09 | Finding out on exactly what I am stuck |
| Previous Message | Mike angelo | 2009-04-09 15:47:10 | pg_toast |