pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: d.wall@computer.org
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL copying includes vacuum, reindex, etc?
Date: Tue, 15 Jan 2008 13:07:32 -0500
Message-ID: <26472.1200420452@sss.pgh.pa.us> (raw)
In-Reply-To: <1200418532.4266.1767.camel@ebony.site>
References: <478CEB2E.4040601@computer.org>
	<1200418532.4266.1767.camel@ebony.site>

Simon Riggs <simon@2ndquadrant.com> 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



view thread (3+ messages)

Message-ID: <26472.1200420452@sss.pgh.pa.us>
Permalink:  ../26472.1200420452@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26472.1200420452@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, d.wall@computer.org
  Subject: Re: WAL copying includes vacuum, reindex, etc?
  In-Reply-To: <26472.1200420452@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox