From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
Date: Thu, 13 Dec 2007 15:19:34 -0600
Message-ID: <47614D86.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <1197569564.4255.1855.camel@ebony.site>
References: <4760FF69.EE98.0025.0@wicourts.gov>
<1197562283.4255.1829.camel@ebony.site>
<47611B9D.EE98.0025.0@wicourts.gov>
<1197569564.4255.1855.camel@ebony.site>
>>> On Thu, Dec 13, 2007 at 12:12 PM, in message
<camel@ebony.site/">1197569564.4255.1855.camel@ebony.site>, Simon Riggs <simon@2ndquadrant.com>
wrote:
> On Thu, 2007-12-13 at 11:46 -0600, Kevin Grittner wrote:
>> If the hint bit changes are written to the WAL ...
>
> They're not.
So one would expect a write-intensive initial vacuum after a
PITR-style recovery?
What impact would lack of the hint bits have until a vacuum?
-Kevin
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-performance@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, simon@2ndquadrant.com
Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
In-Reply-To: <47614D86.EE98.0025.0@wicourts.gov>
* 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