Re: Replication Syatem - Mailing list pgsql-performance

From Peter Childs
Subject Re: Replication Syatem
Date
Msg-id a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com
Whole thread Raw
In response to Replication Syatem  ("Gauri Kanekar" <meetgaurikanekar@gmail.com>)
Responses Re: Replication Syatem
List pgsql-performance


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.

pgsql-performance by date:

Previous
From: "Gauri Kanekar"
Date:
Subject: Replication Syatem
Next
From: "Gauri Kanekar"
Date:
Subject: Re: Replication Syatem