From: Gauri Kanekar <meetgaurikanekar@gmail.com>
To: Peter Childs <peterachilds@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Mon, 28 Apr 2008 19:35:37 +0530
Message-ID: <7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com> (raw)
In-Reply-To: <a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com>
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
On Mon, Apr 28, 2008 at 7:28 PM, Peter Childs <peterachilds@gmail.com>
wrote:
>
>
> 2008/4/28 Gauri Kanekar <meetgaurikanekar@gmail.com>:
>
> All,
> >
> > We have a table "table1" which get insert and updates daily in high
> > numbers, bcoz of which its size is increasing and we have to vacuum it every
> > alternate day. Vacuuming "table1" take almost 30min and during that time the
> > site is down.
> >
> > We need to cut down on this downtime.So thought of having a replication
> > system, for which the replicated DB will be up during the master is getting
> > vacuumed.
> >
> > Can anybody guide which will be the best suited replication solution for
> > this.
> >
> > Thanx for any help
> > ~ Gauri
> >
>
> I home your not using Vacuum Full....... (Standard Reply for this type of
> question)
>
> What version of Postgresql are you using?
>
> Have you tried autovacuum?
>
> Run plain vacuum even more often on this even more often (like ever half
> hour) and it should not take as long and save space.
>
> If still have trouble run "vacuum analyse verbose table1;" and see what it
> says.
>
> If your doing it right you should be able to vacuum with the database up.
>
> Sounds like you might be happier a fix for the problem rather than a
> complex work around which will actually solve a completely different
> problem.
>
> Regards
>
> Peter.
>
--
Regards
Gauri
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: meetgaurikanekar@gmail.com, peterachilds@gmail.com
Subject: Re: Replication Syatem
In-Reply-To: <7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@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