Re: Replication Syatem

------=_Part_3821_32133511.1209391094399
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

2008/4/28 Gauri Kanekar <meetgaurikanekar@[EMAIL PROTECTED]
>:

> 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.

------=_Part_3821_32133511.1209391094399
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><br><div class="gmail_quote">2008/4/28 Gauri Kanekar &lt;<a
href="mailto:meetgaurikanekar@[EMAIL PROTECTED]
">meetgaurikanekar@[EMAIL PROTECTED]
>&gt;:<br><blockquote
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204);
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
All,<br><br>We have a table &quot;table1&quot; 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 &quot;table1&quot; take
almost 30min and during that time the site is down.<br>

<br>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.<br clear="all"><br>Can anybody guide which
will be the best suited replication solution for this.<br>

<br>Thanx for any help<br><font color="#888888">~ Gauri<br>
</font></blockquote></div><br>I home your not using Vacuum Full.......
(Standard Reply for this type of question)<br><br>What version of
Postgresql are you using?<br><br>Have you tried autovacuum?<br><br>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.<br>
<br>If still have trouble run &quot;vacuum analyse verbose table1;&quot;
and see what it says.<br><br>If your doing it right you should be able to
vacuum with the database up.<br><br>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.<br>
<br>Regards<br><br>Peter.<br>

------=_Part_3821_32133511.1209391094399--