pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Gregory Stark <stark@enterprisedb.com>
To: rafael@akyasociados.com.ar
Cc: mpartio@gmail.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Vacum Analyze problem
Date: Wed, 05 Sep 2007 00:24:32 +0100
Message-ID: <87bqci580f.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <1415.192.168.1.229.1188927997.squirrel@webmail.akyasociados.com.ar>
References: <2ca799770709041033n664cb0ep3a5679548dac3a2e@mail.gmail.com>
	<1415.192.168.1.229.1188927997.squirrel@webmail.akyasociados.com.ar>

<rafael@akyasociados.com.ar> writes:

> I knew that in the long run the VACUUM ANALYZE comand has to be executed
> again. My question is if something can happen over night and cause the need
> of a new VACUUM ANALYZE (regenerating indexes or other thing related with
> performance).

The answer to your question is possibly yes for two reasons:

1) If you're running an autovacuum daemon it might decide it's time to vacuum
the table and kick off a vacuum. That sounds most like what you're describing.

2) If the size of the table changes substantially becoming much larger (or
smaller but that wouldn't happen just due to deletes unless you run vacuum)
then recent versions of Postgres will notice even if you don't run analyze and
take that into account.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com



view thread (8+ messages)

Message-ID: <87bqci580f.fsf@oxford.xeocode.com>
Permalink:  ../87bqci580f.fsf@oxford.xeocode.com/
Also on:    postgresql.org/message-id/87bqci580f.fsf@oxford.xeocode.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: stark@enterprisedb.com, rafael@akyasociados.com.ar, mpartio@gmail.com
  Subject: Re: Vacum Analyze problem
  In-Reply-To: <87bqci580f.fsf@oxford.xeocode.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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