From: Jaime Casanova <systemguards@gmail.com>
To: Szabolcs BALLA <szballa@confinsystems.com>
Cc: postgre <pgsql-admin@postgresql.org>
Subject: Re: Vacuum is needed or not?
Date: Thu, 5 Jan 2006 10:48:02 -0500
Message-ID: <c2d9e70e0601050748j75b26a82r3c68532aa04ec4e4@mail.gmail.com> (raw)
In-Reply-To: <1136475086.4221.48.camel@bh>
References: <1136466721.4221.39.camel@bh>
<c2d9e70e0601050637i4888ee80gdc25f285f18bec13@mail.gmail.com>
<1136475086.4221.48.camel@bh>
On 1/5/06, Szabolcs BALLA <szballa@confinsystems.com> wrote:
>
>
VACUUM is needed at least every billion transactions...
execute it in a
> script periodically... if you are in doubt if you need
VACUUM then you need
> it urgently, execute it right now!!!
>
> yes, and i running every weekend a full analyze, but actually i think it's
> need again, but just for feel i couldn't stop the server.
> I need evidence. (oldspice rulez ;))
>
> Szabek
a plain VACUUM (without full) is enough in most cases... and you don't
need to stop the server for a plain VACUUM...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: systemguards@gmail.com, szballa@confinsystems.com
Subject: Re: Vacuum is needed or not?
In-Reply-To: <c2d9e70e0601050748j75b26a82r3c68532aa04ec4e4@mail.gmail.com>
References: <1136466721.4221.39.camel@bh> <c2d9e70e0601050637i4888ee80gdc25f285f18bec13@mail.gmail.com> <1136475086.4221.48.camel@bh> <c2d9e70e0601050748j75b26a82r3c68532aa04ec4e4@mail.gmail.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