Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id D816C2E003C for ; Tue, 29 Apr 2008 02:47:03 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 35123-07 for ; Tue, 29 Apr 2008 02:46:57 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by developer.postgresql.org (Postfix) with ESMTP id CE0F62E002D for ; Tue, 29 Apr 2008 02:46:58 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n7so8612171wag.5 for ; Mon, 28 Apr 2008 22:46:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=kGBHIMJ3fDIJifcUIgF1MqvBoyGcqjZQh+rf/x0bG34=; b=B2NzqpWMcmlaZAYUsSsIv02hqxOjRToRDrunoFd0+mn1+NdJZWsvZd19Kw7EGHGCkpda5u5xipELXN/P5ybnAvK66FgNwLlJkhPANs24Qd/WHcxHbpciMS06Qujm/igaux/dC3Z+nDyxls1Lt/JngIjUl0mXhlw3m+mdyXfnN38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=j3Gd96OU8JAg+yUVCVdafkbJkqOLOEjawh/QZotbbpaLaxSbVTr278weUXX3YXtPYFcB+nOst7PwsfDvaRtovSaQrJ4G4F8KFTu8AOvF1PE+fmp3jcvRq2uEgKn+TsMxTf7Cu3UY38aeCPpKW+eBVphoH08aCJk9Jyxi4RuR2rU= Received: by 10.114.154.1 with SMTP id b1mr7522858wae.34.1209448017301; Mon, 28 Apr 2008 22:46:57 -0700 (PDT) Received: by 10.114.240.17 with HTTP; Mon, 28 Apr 2008 22:46:57 -0700 (PDT) Message-ID: <7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@mail.gmail.com> Date: Tue, 29 Apr 2008 11:16:57 +0530 From: "Gauri Kanekar" To: "Andrew Sullivan" , pgsql-performance@postgresql.org Subject: Re: Replication Syatem In-Reply-To: <20080428162243.GN2970@commandprompt.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10564_30708371.1209448017294" References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com> <7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com> <20080428162243.GN2970@commandprompt.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.9 tagged_above=0 required=5 tests=FS_REPLICA=1.179, HTML_MESSAGE=0.001, SARE_SPEC_REPLICA=0.72 X-Spam-Level: * X-Archive-Number: 200804/424 X-Sequence-Number: 29917 ------=_Part_10564_30708371.1209448017294 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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 ------=_Part_10564_30708371.1209448017294 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_10564_30708371.1209448017294--