pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Russell Smith <mr-russ@pws.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
Date: Fri, 14 Dec 2007 09:19:11 -0600
Message-ID: <47624A8E.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <29185.1197618162@sss.pgh.pa.us>
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>
	<47614D86.EE98.0025.0@wicourts.gov>
	<1197582010.4255.1912.camel@ebony.site>
	<47623103.7030700@pws.com.au>
	<47623103.7030700@pws.com.au>
	<29185.1197618162@sss.pgh.pa.us>

>>> On Fri, Dec 14, 2007 at  1:42 AM, in message <29185.1197618162@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> wrote: 
 
> My feeling is that vacuum's purpose in life is to offload maintenance
> cycles from foreground queries, so we should be happy to have it setting
> all the hint bits.
 
Absolutely.
 
> If Kevin doesn't like the resultant I/O load then he
> should use the vacuum_cost_delay parameters to dial down vacuum speed.
 
It's not that I don't like it -- I'm often called upon to diagnose
issues, and understanding the dynamics of things like this helps me
interpret what I'm seeing.  No complaint here.
 
-Kevin
 

view thread (21+ messages)  latest in thread

Message-ID: <47624A8E.EE98.0025.0@wicourts.gov>
Permalink:  ../47624A8E.EE98.0025.0@wicourts.gov/
Also on:    postgresql.org/message-id/47624A8E.EE98.0025.0@wicourts.gov

copy link · copy postgr.es

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-performance@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, mr-russ@pws.com.au, tgl@sss.pgh.pa.us, simon@2ndquadrant.com
  Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
  In-Reply-To: <47624A8E.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