Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 13 Dec 2007 10:39:47 -0600
>>> 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
- Follow-Ups:
- Re: Heavy write activity on first vacuum of fresh TOAST data
- From: Simon Riggs
- Re: Heavy write activity on first vacuum of fresh TOAST data
- References:
- Heavy write activity on first vacuum of fresh TOAST data
- From: Kevin Grittner
- Re: Heavy write activity on first vacuum of fresh TOAST data
- From: Simon Riggs
- Re: Heavy write activity on first vacuum of fresh TOAST data
- From: Kevin Grittner
- Re: Heavy write activity on first vacuum of fresh TOAST data
- From: Tom Lane
- Heavy write activity on first vacuum of fresh TOAST data
- Prev by Date: Re: Heavy write activity on first vacuum of fresh TOAST data
- Next by Date: Re: Heavy write activity on first vacuum of fresh TOAST data
- Previous by thread: Re: Heavy write activity on first vacuum of fresh TOAST data
- Next by thread: Re: Heavy write activity on first vacuum of fresh TOAST data
- Indexes: