Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id B868D2E0033 for ; Tue, 29 Apr 2008 10:09:50 -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 93228-01 for ; Tue, 29 Apr 2008 10:09:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by developer.postgresql.org (Postfix) with ESMTP id 513D22E0032 for ; Tue, 29 Apr 2008 10:09:43 -0300 (ADT) Received: by yw-out-2324.google.com with SMTP id 5so1673849ywb.73 for ; Tue, 29 Apr 2008 06:09:39 -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:content-transfer-encoding:content-disposition:references; bh=g/H3ml4duBUgzKSLQz9NyItxkQjNEpkPX9dWopgI5ag=; b=O/cZ+rTE7wFTnRW1gGqk0oMmYDzG520Ic4g2e0KqxJTqxgxqA6c2yGHVkf3yImijU/0lHPp8tGts2G3A85Sc+1q6p5d/MF2fWhcK9mxAktbQ+Jq+prnBQyg/QqdDRalLwoprJ/7s+ceG2TKUZOiFdoSlMs5tUHox3RcATaAdpQE= 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:content-transfer-encoding:content-disposition:references; b=rbZNE23Y6fkKGZDNtACcZpwCuD7GUSsY3xTWZmO0e/8nfn+kvz4fg91Vdtnz1Fo2s5ojeapSDEA/jyP9NyIHk+MMp63jWU+YmgfVXB598fV8UTwZD6T65O1BHLa5VsltRYJKFnThcYgtv+hUlnohbu/Uum6khhLTFX8WMUN/irU= Received: by 10.150.79.32 with SMTP id c32mr4993020ybb.156.1209474579811; Tue, 29 Apr 2008 06:09:39 -0700 (PDT) Received: by 10.151.84.7 with HTTP; Tue, 29 Apr 2008 06:09:39 -0700 (PDT) Message-ID: <2e78013d0804290609k3bd2aa94q8c6b1c9763e2355a@mail.gmail.com> Date: Tue, 29 Apr 2008 18:39:39 +0530 From: "Pavan Deolasee" To: "Gauri Kanekar" Subject: Re: Replication Syatem Cc: "Greg Smith" , pgsql-performance@postgresql.org In-Reply-To: <7e4ba9550804290559t7948d549j7e506154c0b1ed38@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.504 tagged_above=0 required=5 tests=AWL=-1.395, FS_REPLICA=1.179, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 200804/437 X-Sequence-Number: 29930 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