pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
When to ANALYZE w/ auto-vacuum
2+ messages / 2 participants
[nested] [flat]

* When to ANALYZE w/ auto-vacuum
@ 2008-02-10 04:34 Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
  2008-02-10 06:11 ` Re: When to ANALYZE w/ auto-vacuum Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: Dean Gibson (DB Administrator) @ 2008-02-10 04:34 UTC (permalink / raw)
  To: pgsql-admin

Now, that I have 8.3.0 installed & running auto-vacuum, I have gotten 
rid of all my scripted VACUUMs, and I would like to get rid of all the 
scripted ANALYZEs as well.  The 8.3 docs say:

    "In the default PostgreSQL configuration, /The Auto-Vacuum Daemon/
    <https://web.ultimeth.com/doc/private/postgreSQL/routine-vacuuming.html#AUTOVACUUM;
    takes care of automatic analyzing of tables when they are first
    loaded with data, and as they change throughout regular operation."


However:

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.

-- Dean



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: When to ANALYZE w/ auto-vacuum
  2008-02-10 04:34 When to ANALYZE w/ auto-vacuum Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
@ 2008-02-10 06:11 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2008-02-10 06:11 UTC (permalink / raw)
  To: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>; +Cc: pgsql-admin

"Dean Gibson (DB Administrator)" <postgresql@ultimeth.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



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2008-02-10 06:11 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-02-10 04:34 When to ANALYZE w/ auto-vacuum Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
2008-02-10 06:11 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox