Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 4CF9D2E002D for ; Wed, 14 May 2008 23:38:14 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 27741-03 for ; Wed, 14 May 2008 23:38:04 -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.182]) by developer.postgresql.org (Postfix) with ESMTP id 2724F2E003A for ; Wed, 14 May 2008 23:38:09 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n4so253157wag.5 for ; Wed, 14 May 2008 19:38:08 -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:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=L5ga9Sbn8jFrWxNAPZHzjtKWoHaANzZnNQS8OEz9l7Q=; b=l1ixYpajvLKedMTUDEzR+vWh6beoRWKcAkEOIlwPyBkFJRJfDshxwhtUiK5OGMglAaBpr/5+BjEHN6AKkb/IUPFhYd1MeSnL11FOYZOMfv3HoTXWlwUWsZB2Ozlk44rlcoT05RXht/7R3Oz7zyyQmi9eex6UgmmcGXyBIH4iuMg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=HONnEAb41rzps5LXjsN1mPHKgBcGQswlzSDEYnvSppQg9hfRnV6yTrUkflBPFb2/thQgPQGtIKU8cYCqzXzl1MF2u1Bx0xCTmMPdRQYuba5XmzlvATxiuspCZryveoHINDIijs+r2p6SgGVIyIy/4FH73Ghh5YhqxMSEDGYZfQA= Received: by 10.114.153.18 with SMTP id a18mr1890079wae.127.1210819088541; Wed, 14 May 2008 19:38:08 -0700 (PDT) Received: by 10.115.92.16 with HTTP; Wed, 14 May 2008 19:38:08 -0700 (PDT) Message-ID: <1159c1e90805141938j5f85b490rb5c1cfdf9e428bce@mail.gmail.com> Date: Wed, 14 May 2008 22:38:08 -0400 From: "Jan de Visser" To: "Greg Smith" Subject: Re: I/O on select count(*) Cc: "Alvaro Herrera" , pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <920841.71690.qm@web44808.mail.sp1.yahoo.com> <482B1D5F.EE98.0025.0@wicourts.gov> <20080515020553.GN9838@alvh.no-ip.org> X-Google-Sender-Auth: 496724cf613df46b X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/192 X-Sequence-Number: 30160 On 5/14/08, Greg Smith wrote: > On Wed, 14 May 2008, Alvaro Herrera wrote: > > > > If neither of the bits is set, then the transaction is either in progress > (which you can check by examining the list of running transactions in shared > memory) or your process is the first one to check (in which case, you need > to consult pg_clog to know the status, and you can update the hint bits if > you find out a permanent state). > > > > So is vacuum helpful here because it will force all that to happen in one > batch? To put that another way: if I've run a manual vacuum, is it true > that it will have updated all the hint bits to XMIN_COMMITTED for all the > tuples that were all done when the vacuum started?