Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4A153650EC2 for ; Wed, 2 Jul 2008 11:48:46 -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 64216-01-3 for ; Wed, 2 Jul 2008 11:48:32 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by postgresql.org (Postfix) with ESMTP id 4B2D8650EDB for ; Wed, 2 Jul 2008 11:48:12 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n4so251822wag.5 for ; Wed, 02 Jul 2008 07:48:11 -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=zs7ANeivGKalUy5PfmMDcTHQ7biNC81SMPvPWe+XfIg=; b=UFpb7sIrPxhpv5z4TXPycfjESNQuGQ6YwF8QO/veInmVFAsCoD+Dod0caEZ6h4CTzW S5RNigm2XbQKXyJyk7cN/MNYuG3K/64yVesoZNuFIfc9tot+LDI0YUaG73le/CPH7uVF 1nP2lE9jskq/0GLXI/cq6p4uCxkmSz+mAPlGU= 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=wQMRqzNJrpD+EFQwTW9a8KzjybPautJLOZpPr7GerpHCBkM9j5OKAgEhWOi3meEJt6 kFZgwlua5dIhl9b8Mk1I9rfBbBeZNk2ClpuzTS2b4ZfMy39i6yBHQSyZWmFTnyTp3WQn sLDYyuviR7cVj6lDkgiIXuAdjUIr0dmTPFRxY= Received: by 10.114.148.2 with SMTP id v2mr7057592wad.173.1215010091122; Wed, 02 Jul 2008 07:48:11 -0700 (PDT) Received: by 10.115.60.2 with HTTP; Wed, 2 Jul 2008 07:48:11 -0700 (PDT) Message-ID: <7e4ba9550807020748r5b4749c2i6148d62573722368@mail.gmail.com> Date: Wed, 2 Jul 2008 20:18:11 +0530 From: "Gauri Kanekar" To: "Tom Lane" Subject: Re: Hot Issue Cc: "Jonah H. Harris" , "=?ISO-8859-1?Q?Devrim_G=DCND=DCZ?=" , pgsql-performance@postgresql.org In-Reply-To: <11126.1215009603@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2905_32252480.1215010091129" References: <7e4ba9550807020531w5480956fs2a1b5b630babda41@mail.gmail.com> <1215004084.2842.32.camel@laptop.gunduz.org> <7e4ba9550807020611x3dac7fffw8497d168c7a0e9d8@mail.gmail.com> <36e682920807020629h2b0432e9k39cc01f1693e6a40@mail.gmail.com> <7e4ba9550807020644j4f41530axd43317c7f180faed@mail.gmail.com> <36e682920807020721s3e537ef8k3189c8ce3b47e6c7@mail.gmail.com> <11126.1215009603@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.747 tagged_above=0 required=5 tests=AWL=0.746, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200807/29 X-Sequence-Number: 30629 ------=_Part_2905_32252480.1215010091129 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2nd count include the 1st count also. We have not restarted the DB since postgres 8.3 have been released. Better HOT performance means.... 1st stat showed most of the updated tuples getting hot. But the 2nd stat showed that most of the updated tuples are NOT getting hot. On Wed, Jul 2, 2008 at 8:10 PM, Tom Lane wrote: > "Jonah H. Harris" writes: > > On Wed, Jul 2, 2008 at 9:44 AM, Gauri Kanekar > >> 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. > > You could make your application check to see if the page part of a row's > CTID changes when it's updated. But there's no centralized counter > other than the one you are already looking at. > > I personally found the original post completely content-free, however, > since it gave no context for the two sets of numbers we were shown. > Over what intervals were the counts accumulated? Were the stats > counters reset after taking the first output, or does the second output > include the first? What exactly does the OP think that "better HOT > performance" is, anyway? > > regards, tom lane > -- Regards Gauri ------=_Part_2905_32252480.1215010091129 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
2nd count include the 1st count also.

We have not restarted the DB since postgres 8.3 have been released.

Better HOT performance means.... 1st stat showed most of the updated tuples getting hot.
But the 2nd stat showed that most of the updated tuples are NOT getting hot.



On Wed, Jul 2, 2008 at 8:10 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Jonah H. Harris" <jonah.harris@gmail.com> writes:
> On Wed, Jul 2, 2008 at 9:44 AM, Gauri Kanekar
>> 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.

You could make your application check to see if the page part of a row's
CTID changes when it's updated.  But there's no centralized counter
other than the one you are already looking at.

I personally found the original post completely content-free, however,
since it gave no context for the two sets of numbers we were shown.
Over what intervals were the counts accumulated?  Were the stats
counters reset after taking the first output, or does the second output
include the first?  What exactly does the OP think that "better HOT
performance" is, anyway?

                       regards, tom lane



--
Regards
Gauri ------=_Part_2905_32252480.1215010091129--