Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E3A48650F08 for ; Wed, 2 Jul 2008 11:22:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 37511-03 for ; Wed, 2 Jul 2008 11:22:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.190]) by postgresql.org (Postfix) with ESMTP id 8EA73650EC2 for ; Wed, 2 Jul 2008 11:21:16 -0300 (ADT) Received: by rn-out-0910.google.com with SMTP id k40so94001rnd.0 for ; Wed, 02 Jul 2008 07:21:14 -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=tLcygbx52J0rsr4kt71/SE6tgRnijM+JpnPORwZ6Ctw=; b=tx9EO6oGSg1/0RKoiyrW4cEx+zFGJ7BPcXmFtRewrrMPG2m0Gq/M71kBgYD3JT7pxQ rpuOyrEVeETS55jSdTcfLUwLEFok/4U1sTu5DyRBJ+L+blpQbgUfZWHWrEeSbmRyEWnP 1aQrmz+uXsHPhrP5Qb76PMXrzB1GBBViIOWKU= 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=Lo1ubGqLbda0He0XSi7nOc+ZYQXpj7EROBgEu7Gx6UK/k4sy3/R5Hk8JCW9lzA/3LZ niBEzgDE/vmm+xlXiwktGv9B9zpFjsjr/hWmAvdWdMxTsFIBqKXF149XCMJjh16/VkaS XIBI5EDp02PdNHRSSw0DKYDtG5PWOaaUtEM7M= Received: by 10.150.151.20 with SMTP id y20mr13134305ybd.78.1215008474322; Wed, 02 Jul 2008 07:21:14 -0700 (PDT) Received: by 10.150.186.15 with HTTP; Wed, 2 Jul 2008 07:21:14 -0700 (PDT) Message-ID: <36e682920807020721s3e537ef8k3189c8ce3b47e6c7@mail.gmail.com> Date: Wed, 2 Jul 2008 10:21:14 -0400 From: "Jonah H. Harris" To: "Gauri Kanekar" Subject: Re: Hot Issue Cc: "=?ISO-8859-1?Q?Devrim_G=DCND=DCZ?=" , pgsql-performance@postgresql.org In-Reply-To: <7e4ba9550807020644j4f41530axd43317c7f180faed@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7e4ba9550807020531w5480956fs2a1b5b630babda41@mail.gmail.com> <1215004084.2842.32.camel@laptop.gunduz.org> <7e4ba9550807020611x3dac7fffw8497d168c7a0e9d8@mail.gmail.com> <36e682920807020629h2b0432e9k39cc01f1693e6a40@mail.gmail.com> <7e4ba9550807020644j4f41530axd43317c7f180faed@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/27 X-Sequence-Number: 30627 On Wed, Jul 2, 2008 at 9:44 AM, Gauri Kanekar wrote: > ok.. But we have set fill_factor = 80 for all the indexes on table1. You need fill factor for the heap table, not the index. > Is there a way to check if the page is fill and the update is going on a new > page ?? IIRC, I don't think so. I think you'd have to u se something like pg_filedump to see if you have rows migrated to other blocks due to updates. -- Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com Edison, NJ 08837 | http://www.enterprisedb.com/