| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum and toast tables |
| Date: | 2007-08-13 22:47:27 |
| Message-ID: | 23770.1187045247@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I think there is some special code in tqual.c that skips some checks
> assuming that the toast table is vacuumed at the same time as the main
> heap.
I don't believe there is any such connection. We do use a special
snapshot for toast tables, but it's only needed to make sure VACUUM FULL
on a toast table will work (ie, we have to respect MOVED_IN/MOVED_OFF).
> We go certain lengths in autovacuum to make sure tables are vacuumed
> when their toast table needs vacuuming and the main table does not,
> which is all quite kludgy.
Yeah --- getting rid of that mess would be a plus.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2007-08-13 23:08:02 | Re: [HACKERS] Proposal: Pluggable Optimizer Interface |
| Previous Message | Alvaro Herrera | 2007-08-13 22:32:12 | Re: Autovacuum and toast tables |