Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4B3532E3098 for ; Tue, 15 Jan 2008 14:07:50 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 92971-06 for ; Tue, 15 Jan 2008 14:07:44 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id E32F22E300F for ; Tue, 15 Jan 2008 14:07:44 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id m0FI7WXN026473; Tue, 15 Jan 2008 13:07:32 -0500 (EST) To: Simon Riggs cc: d.wall@computer.org, pgsql-admin@postgresql.org Subject: Re: WAL copying includes vacuum, reindex, etc? In-reply-to: <1200418532.4266.1767.camel@ebony.site> References: <478CEB2E.4040601@computer.org> <1200418532.4266.1767.camel@ebony.site> Comments: In-reply-to Simon Riggs message dated "Tue, 15 Jan 2008 17:35:32 +0000" Date: Tue, 15 Jan 2008 13:07:32 -0500 Message-ID: <26472.1200420452@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/165 X-Sequence-Number: 27939 Simon Riggs writes: > All of those commands produce WAL for critical changes to data blocks, > so those are passed through correctly. > Hint bits are not set following recovery, so a full database VACUUM may > help later performance, depends upon your access patterns. That's only partially true. Full-page images in WAL will propagate hint bits, so in practice you could expect that only about one checkpoint cycle's worth of hint information is missing. If you'd been running with full_page_writes = off then this doesn't hold, and in that case I'd agree that a forced vacuum might be worth the trouble. regards, tom lane