From: Gauri Kanekar <meetgaurikanekar@gmail.com>
To: Andrew Sullivan <ajs@commandprompt.com>
To: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Tue, 29 Apr 2008 11:16:57 +0530
Message-ID: <7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@mail.gmail.com> (raw)
In-Reply-To: <20080428162243.GN2970@commandprompt.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com>
<7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com>
<20080428162243.GN2970@commandprompt.com>
Andrew,
Can you explain me in detail why u said vacuum full is making the things
worst.
We do vacuum full, as vacuum verbose analyse dont regain space for us.
~ Gauri
On Mon, Apr 28, 2008 at 9:52 PM, Andrew Sullivan <ajs@commandprompt.com>
wrote:
> On Mon, Apr 28, 2008 at 07:35:37PM +0530, Gauri Kanekar wrote:
> > Peter,
> >
> > We are doing vacuum full every alternate day. We also do vacuum analyze
> very
> > often.
>
> VACUUM FULL is making your problem worse, not better. Don't do that.
>
> > We are currently using 8.1.3 version.
>
> You need immediately to upgrade to the latest 8.1 stability and
> security release, which is 8.1.11. This is a drop-in replacement.
> It's an urgent fix for your case.
>
> > Auto vacuum is already on. But the table1 is so busy that auto vacuum
> don't
> > get sufficient chance to vacuum it :(.
>
> You probably need to tune autovacuum not to do that table, and just
> vacuum that table in a constant loop or something. VACUUM should
> _never_ "take the site down". If it does, you're doing it wrong.
>
> > 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 :).
>
> I think you will find that no replication system will solve your
> underlying problems. That said, I happen to work for a company that
> will sell you a replication system to work with 8.1 if you really want
> it.
>
> A
>
>
> --
> Andrew Sullivan
> ajs@commandprompt.com
> +1 503 667 4564 x104
> http://www.commandprompt.com/
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
--
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, ajs@commandprompt.com
Subject: Re: Replication Syatem
In-Reply-To: <7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@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