| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: autovacuum doesnt run on the pg_toast_id table |
| Date: | 2019-01-17 17:46:51 |
| Message-ID: | 20190117174651.GC18438@telsasoft.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jan 17, 2019 at 07:28:52PM +0200, Mariel Cherkassky wrote:
...
> Now, I realized from the autovacuum
> logging, that when autovacuum runs on the original table (A) it doesn't
> necessary run on the toasted table and this is very weird.
...
> Any idea why the autovacuum doesnt vacuum both tables ?
It *does* vacuum both, just not *necessarily*, as you saw.
The toast is a separate table, so it's tracked separately.
Note that:
|If a table parameter value is set and the
|equivalent <literal>toast.</literal> parameter is not, the TOAST table
|will use the table's parameter value.
You could look in pg_stat_all_tables, to see how frequently the toast is being
autovacuumed relative to its table.
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-01-17 17:52:41 | Re: autovacuum doesnt run on the pg_toast_id table |
| Previous Message | Mariel Cherkassky | 2019-01-17 17:28:52 | autovacuum doesnt run on the pg_toast_id table |