From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dean Gibson (DB Administrator)" <postgresql(at)ultimeth(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: When to ANALYZE w/ auto-vacuum |
Date: | 2008-02-10 06:11:00 |
Message-ID: | 8381.1202623860@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Dean Gibson (DB Administrator)" <postgresql(at)ultimeth(dot)com> writes:
> 1. There is one nightly process I run where I create a fairly large TEMP
> table (well over 1 million rows), and then I immediately use it in a
> subsequent SELECT. Would a scripted ANALYZE be really needed here, or
> does the auto-vacuum track the large TEMP table as I create it (via a
> single SELECT).
> 2. For that manner, do TEMP tables get higher priority in auto-vacuum
> runs? That would seem to be a good idea.
autovacuum cannot touch other sessions' temp tables at all --- it
physically doesn't have access to them. (To give it such access would
require destroying most of the performance advantages of making a table
temp in the first place.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Morozovsky | 2008-02-10 15:15:39 | changing default object rights |
Previous Message | Dean Gibson (DB Administrator) | 2008-02-10 04:34:16 | When to ANALYZE w/ auto-vacuum |