Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? ) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )
Date
Msg-id 29685.1250205715@sss.pgh.pa.us
Whole thread Raw
In response to Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )  (Josh Berkus <josh@agliodbs.com>)
Responses Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
>> What are you envisioning exactly?  If vacuum finds any reason to dirty
>> a page (or it's already dirty), then freeze everything on the page that's
>> got age > some lower threshold?

> I was envisioning, if the page is already dirty and in memory *for any
> reason*, the freeze rows at below some threshold.

I believe we've had this discussion before.  I do *NOT* want freezing
operations pushed into any random page access, and in particular will
do my best to veto any attempt to put them into the bgwriter.  Freezing
requires accessing the clog and emitting a WAL record, and neither is
appropriate for low-level code like bgwriter.  The deadlock potential
alone is sufficient reason why not.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )
Next
From: Greg Stark
Date:
Subject: Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )