Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 359F82E3794 for ; Tue, 15 Jan 2008 13:35:27 -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 75891-09 for ; Tue, 15 Jan 2008 13:35:17 -0400 (AST) Received: from outmail136058.authsmtp.co.uk (outmail136058.authsmtp.co.uk [62.13.136.58]) by postgresql.org (Postfix) with ESMTP id DC8F62E313D for ; Tue, 15 Jan 2008 13:35:15 -0400 (AST) Received: from outmail128184.authsmtp.net (outmail128184.authsmtp.net [62.13.128.184]) by punt2.authsmtp.com (8.13.8/8.13.8/Kp) with ESMTP id m0FHYwVS060864; Tue, 15 Jan 2008 17:34:58 GMT Received: from [192.168.0.3] (81-6-228-215.dyn.gotadsl.co.uk [81.6.228.215]) (authenticated bits=0) by mail.authsmtp.com (8.13.8/8.13.8/Kp) with ESMTP id m0FHYvkY053073; Tue, 15 Jan 2008 17:34:57 GMT Subject: Re: WAL copying includes vacuum, reindex, etc? From: Simon Riggs To: d.wall@computer.org Cc: pgsql-admin@postgresql.org In-Reply-To: <478CEB2E.4040601@computer.org> References: <478CEB2E.4040601@computer.org> Content-Type: text/plain Date: Tue, 15 Jan 2008 17:35:32 +0000 Message-Id: <1200418532.4266.1767.camel@ebony.site> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Server-Quench: 3111199e-c390-11dc-9554-001185d377ca X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksadBtFaQBbZ1hf HGQLW1xEUVp7Wmd/ bgIfZQRDZFRMXQ10 UklMXVBXCwUmXBx3 fndYCXBycgZGf30+ ZEdlXz5YXUV7dE90 F1MHFmQGeGZhPDMC WUVdcx5UcAJLdhoR aVd4ByJDAzANdhER MyoSGQV5Ahx7YC9S WhAMK11aQEAAGiMw SgtKAzwkAFAAA20p Ih0gJlMMWA4cLk5l WXNh X-Authentic-SMTP: 61633235383639.squirrel.dmpriest.net.uk:787/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system! X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/163 X-Sequence-Number: 27937 On Tue, 2008-01-15 at 09:19 -0800, David Wall wrote: > When running WAL backups and warm-standby restores (we're currently on > PG 8.2), do the vacuumlo changes, vacuum, analyze and reindex type > commands get pushed through WAL files to the backup? Or will the backup > database not have these maintenance items done? 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. It's probably good for peace of mind too, but it's a long way from being an essential requirement. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com