Skip site navigation (1)
Skip section navigation (2)
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
Peripheral Links
Header And Logo
|
Site Navigation
Replication Syatem
- From: "Gauri Kanekar" <meetgaurikanekar(at)gmail(dot)com>
- To: pgsql-performance(at)postgresql(dot)org
- Subject: Replication Syatem
- Date: Mon, 28 Apr 2008 19:08:56 +0530
- Message-id: <7e4ba9550804280638ie81dc23w472785c83cd38fcf(at)mail(dot)gmail(dot)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
- Follow-Ups:
- Re: Replication Syatem
- From: Chris Browne
- Re: Replication Syatem
- From: Radhika S
- Re: Replication Syatem
- From: Peter Childs
- Re: Replication Syatem
- Prev by Date: Re: [pgsql-advocacy] Benchmarks WAS: Sun Talks about MySQL
- Next by Date: Re: Replication Syatem
- Previous by thread: Simple JOIN problem
- Next by thread: Re: Replication Syatem
- Indexes: