Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 4C6982E004D for ; Tue, 29 Apr 2008 10:12:53 -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 93222-02 for ; Tue, 29 Apr 2008 10:12:37 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by developer.postgresql.org (Postfix) with ESMTP id C3E2C2E0040 for ; Tue, 29 Apr 2008 10:12:44 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id 76so2910398wra.10 for ; Tue, 29 Apr 2008 06:12:42 -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:cc:in-reply-to:mime-version:content-type:references; bh=7/PzxLebmrH5Sr6+7ft7PQRdsn2LeCyFPOrO6tiWTpY=; b=raTwVJpWWtT1llQR/K/sXirWtVNGWD0fucQZDnejMvgFhoC6V8xVLCAdmfSV387LDHhXrTisekqbBlbETPDbxVZiHsy3F/c4VCzLZuWa53ZsMau/Ogau8ZZk0VNhbRKVuMwVBmZcEpnOe4MUVDVnMc+erNKzikTol8B1vlqdxjE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hAOTAh0bhQQ1zpxoYRUUHCzVh1X7N5KI702tn8Eqz7DUGUHcKUuC9kYJeHQg1UlulV4SC/jlggYEpToFuDpfLwAEuj4Ab7Rj9DWpoDqfPblB61XOGgHs3+pmEgazlF5FTnJPgLp7qypaOyIkvxJSytg8zz+vG142/b8+fkwdpqU= Received: by 10.114.80.4 with SMTP id d4mr928499wab.44.1209474760532; Tue, 29 Apr 2008 06:12:40 -0700 (PDT) Received: by 10.114.240.17 with HTTP; Tue, 29 Apr 2008 06:12:40 -0700 (PDT) Message-ID: <7e4ba9550804290612v30ef053bj6a7c2fe5600aba27@mail.gmail.com> Date: Tue, 29 Apr 2008 18:42:40 +0530 From: "Gauri Kanekar" To: "Pavan Deolasee" Subject: Re: Replication Syatem Cc: "Greg Smith" , pgsql-performance@postgresql.org In-Reply-To: <2e78013d0804290609k3bd2aa94q8c6b1c9763e2355a@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1327_31411602.1209474760521" References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com> <7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com> <20080428162243.GN2970@commandprompt.com> <7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@mail.gmail.com> <7e4ba9550804290405i4c0d3a57x1640239c9995c13@mail.gmail.com> <2e78013d0804290425n402f5e94i90bc7206aeefffdc@mail.gmail.com> <7e4ba9550804290559t7948d549j7e506154c0b1ed38@mail.gmail.com> <2e78013d0804290609k3bd2aa94q8c6b1c9763e2355a@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.67 tagged_above=0 required=5 tests=AWL=-1.230, FS_REPLICA=1.179, HTML_MESSAGE=0.001, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 200804/438 X-Sequence-Number: 29931 ------=_Part_1327_31411602.1209474760521 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thats how our updates works. We usually tend to touch the same row many times a day. ~ Gauri On Tue, Apr 29, 2008 at 6:39 PM, Pavan Deolasee wrote: > On Tue, Apr 29, 2008 at 6:29 PM, Gauri Kanekar > wrote: > > > > > > Found that the size increased gradually. Is HOT working over here ?? > > Guide me if im doing something wrong. > > > > You have chosen a bad case for HOT. Since you are repeatedly updating > the same set of rows, the dead space created in the first step is the > blocks which are not touched in the subsequent updates. Is this a real > scenario or are you just testing ? If its just for testing, I would > suggest updating different sets of rows in each step and then check. > > Thanks, > Pavan > > > > -- > Pavan Deolasee > EnterpriseDB http://www.enterprisedb.com > -- Regards Gauri ------=_Part_1327_31411602.1209474760521 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thats how our updates works.
We usually tend to touch the same row many times a day.

~ Gauri

On Tue, Apr 29, 2008 at 6:39 PM, Pavan Deolasee <pavan.deolasee@gmail.com> wrote:
On Tue, Apr 29, 2008 at 6:29 PM, Gauri Kanekar
<meetgaurikanekar@gmail.com> wrote:
>
>
> Found that the size increased gradually. Is HOT working over here ??
> Guide me if im doing something wrong.
>

You have chosen a bad case for HOT. Since you are repeatedly updating
the same set of rows, the dead space created in the first step is the
blocks which are not touched in the subsequent updates. Is this a real
scenario or are you just testing ? If its just for testing, I would
suggest updating different sets of rows in each step and then check.

Thanks,
Pavan



--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com



--
Regards
Gauri ------=_Part_1327_31411602.1209474760521--