From: Peter Childs <peterachilds@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Mon, 28 Apr 2008 14:58:14 +0100
Message-ID: <a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com> (raw)
In-Reply-To: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
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.
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: peterachilds@gmail.com
Subject: Re: Replication Syatem
In-Reply-To: <a2de01dd0804280658t68ac22dsf182d304a94de5a2@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