X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 60483D1B513 for ; Sun, 5 Oct 2003 18:08:00 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 86806-01 for ; Sun, 5 Oct 2003 15:07:14 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 49824D1B4FE for ; Sun, 5 Oct 2003 15:07:13 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h95I7Dhn006653; Sun, 5 Oct 2003 14:07:13 -0400 (EDT) To: "Matt Clark" Cc: "Andrew Sullivan" , pgsql-performance@postgresql.org Subject: Re: reindex/vacuum locking/performance? In-reply-to: References: Comments: In-reply-to "Matt Clark" message dated "Sun, 05 Oct 2003 18:59:14 +0100" Date: Sun, 05 Oct 2003 14:07:13 -0400 Message-ID: <6652.1065377233@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/158 X-Sequence-Number: 3906 "Matt Clark" writes: > OK, I had thought (wrongly it seems, as usual, but this is how we learn!) > that a plain VACUUM did not incur a read of all pages. I still don't > understand *why* it does, but I'll take your word for it. Mainly 'cause it doesn't know where the dead tuples are till it's looked. Also, VACUUM is the data collector for the free space map, and so it is also charged with finding out how much free space exists on every page. regards, tom lane