From: salman <salmanb@quietcaresystems.com>
To: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: Peter Childs <peterachilds@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Mon, 28 Apr 2008 10:16:44 -0400
Message-ID: <4815DC4C.9060509@quietcaresystems.com> (raw)
In-Reply-To: <7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com>
<7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com>
Gauri Kanekar wrote:
> Peter,
>
> We are doing vacuum full every alternate day. We also do vacuum analyze very
> often.
> We are currently using 8.1.3 version.
> Auto vacuum is already on. But the table1 is so busy that auto vacuum don't
> get sufficient chance to vacuum it :(.
>
> Have already tried all the option listed by you, thats y we reached to the
> decision of having a replication sytsem. So any suggestion on that :).
>
> Thanx
> ~ Gauri
>
We use slony for exactly this type of a situation. It's not the most
user-friendly piece of software, but it works well enough that I can
schedule maintenance windows (we're a 24/7 shop) and do clustering and
other tasks on our DB to reclaim space, etc.
-salman
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: salmanb@quietcaresystems.com, meetgaurikanekar@gmail.com, peterachilds@gmail.com
Subject: Re: Replication Syatem
In-Reply-To: <4815DC4C.9060509@quietcaresystems.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