Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 7961EB5D803 for ; Sun, 29 May 2011 14:06:06 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 82284-08 for ; Sun, 29 May 2011 17:05:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 20F38B5D800 for ; Sun, 29 May 2011 14:05:58 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p4TH5rFv022526; Sun, 29 May 2011 13:05:53 -0400 (EDT) To: Pavan Deolasee cc: =?ISO-8859-1?Q?C=E9dric_Villemain?= , Greg Stark , Robert Haas , Kevin Grittner , Florian Helmberger , Alvaro Herrera , pgsql-hackers@postgresql.org Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum In-reply-to: References: <4DD28F73.6010108@25th-floor.com> <25017.1306291669@sss.pgh.pa.us> <4DDCA801.70805@25th-floor.com> <19738.1306338472@sss.pgh.pa.us> <22497.1306341699@sss.pgh.pa.us> <15043.1306423500@sss.pgh.pa.us> <25097.1306426982@sss.pgh.pa.us> <4DDE475B020000250003DD63@gw.wicourts.gov> <4DDE5033020000250003DD71@gw.wicourts.gov> <4DDE7EB8020000250003DDA8@gw.wicourts.gov> <9007.1306446600@sss.pgh.pa.us> <28116.1306609295@sss.pgh.pa.us> <11295.1306645848@sss.pgh.pa.us> <19876.1306680027@sss.pgh.pa.us> Comments: In-reply-to Pavan Deolasee message dated "Sun, 29 May 2011 21:56:40 +0530" Date: Sun, 29 May 2011 13:05:53 -0400 Message-ID: <22525.1306688753@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201105/1501 X-Sequence-Number: 188535 Pavan Deolasee writes: > I am sorry if I sounded terse above. But my gripe is that sometimes we > are too reluctant to listen to ideas and insist on producing some hard > numbers first which might take significant efforts. But we are not > equally strict when such changes are introduced initially. The reason for not wanting to change it without some actual evidence is that there is already evidence: the code has been in the field with this setting since 8.4, and nobody's vacuum performance has fallen off a cliff. So while I'd agree that there was little testing done before the code went in, there is more than zero reason to leave it where it is. Without some positive evidence showing that another value is better, I'm disinclined to change it. I also think that you're not helping by complaining about the code without being willing to do some work to try to collect such evidence. > Heikki suggested 20, Simon proposed 32 to make it a power of 2. But > why not 16 ? Thats closer to 16 than 32. And Greg yesterday said, 8 is > a better number based on his testings. Greg said he had found that the read speed was the same for reading every page vs reading every 8th page. That's not the same as concluding that 8 is the optimal skip distance for vacuum; or at least, he didn't say that's what he had concluded. vacuum isn't just reading ... regards, tom lane