Re: Heavy write activity on first vacuum of fresh TOAST data

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
Date: 2007-12-13 16:39:47
Message-ID: 47610BF3.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>> On Thu, Dec 13, 2007 at 10:35 AM, in message <13267(dot)1197563721(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> ... although to a naive user it's not clear what
>> is known at vacuum time that the INSERT into the empty table
>> couldn't have inferred.
>
> The fact that the INSERT actually committed.

Fair enough. I suppose that the possibility that of access before
the commit would preclude any optimization that would assume the
commit is more likely than a rollback, and do the extra work only in
the unusual case?

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Simon Riggs 2007-12-13 17:00:42 Re: Heavy write activity on first vacuum of fresh TOAST data
Previous Message Tom Lane 2007-12-13 16:35:21 Re: Heavy write activity on first vacuum of fresh TOAST data