Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )
Date: 2009-08-13 23:21:55
Message-ID: 29685.1250205715@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-08-13 23:31:15 Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )
Previous Message Greg Stark 2009-08-13 23:21:47 Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Stark 2009-08-13 23:31:15 Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )
Previous Message Greg Stark 2009-08-13 23:21:47 Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? )