pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org
Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
Date: Thu, 13 Dec 2007 16:11:23 +0000
Message-ID: <1197562283.4255.1829.camel@ebony.site> (raw)
In-Reply-To: <4760FF69.EE98.0025.0@wicourts.gov>
References: <4760FF69.EE98.0025.0@wicourts.gov>

On Thu, 2007-12-13 at 09:46 -0600, Kevin Grittner wrote:
 
> The data was inserted through a Java program using a prepared
> statement with no indexes on the table.  The primary key was then
> added, and now I've started a vacuum.  The new table wound up being
> the first big table vacuumed, and I noticed something odd.  Even
> though there have been no rollbacks, updates, or deletes on this
> table, the vacuum is writing as much as it is reading while dealing
> with the TOAST data.

Writing hint bits. Annoying isn't it? :-(

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com




view thread (21+ messages)  latest in thread

Message-ID: <1197562283.4255.1829.camel@ebony.site>
Permalink:  ../1197562283.4255.1829.camel@ebony.site/
Also on:    postgresql.org/message-id/1197562283.4255.1829.camel@ebony.site

 · 

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: simon@2ndquadrant.com, Kevin.Grittner@wicourts.gov
  Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
  In-Reply-To: <1197562283.4255.1829.camel@ebony.site>

* 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