Re: [HACKERS] freezing tuples ( was: Why is vacuum_freeze_min_age 100m? ) - Mailing list pgsql-performance

From Robert Haas
Subject Re: [HACKERS] freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )
Date
Msg-id 603c8f070908131525o54e95dbbna868c370485c9381@mail.gmail.com
Whole thread Raw
In response to freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-performance
On Thu, Aug 13, 2009 at 5:33 PM, Jeff Davis<pgsql@j-davis.com> wrote:
> Or, perhaps when the bgwriter is flushing dirty buffers, it can look for
> opportunities to set hint bits or freeze tuples.

One of the tricky things here is that the time you are mostly likely
to want to do this is when you are loading a lot of data.  But in that
case shared buffers are likely to be written back to disk before
transaction commit, so it'll be too early to do anything.

...Robert

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: [HACKERS] freezing tuples ( was: Why is vacuum_freeze_min_age100m? )
Next
From: Josh Berkus
Date:
Subject: Re: Re: [HACKERS] freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )