"Dean Gibson (DB Administrator)" <postgresql@xxxxxxxxxxxx> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
