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

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

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> Yes. There are two ways to do the threshold:
> 1. Constant fraction of vacuum_freeze_min_age
> 2. Extra GUC

> I lean toward #1, because it avoids an extra GUC*, and it avoids the
> awkwardness when the "lower" setting is higher than the "higher"
> setting.

I tend to agree with Josh that you do need to offer two knobs. But
expressing the second knob as a fraction (with range 0 to 1) might be
better than an independent "min" parameter. As you say, that'd be
useful to prevent people from setting them inconsistently.

> *: As an aside, these GUCs already have incredibly confusing names, and
> an extra variable would increase the confusion. For instance, they seem
> to use "min" and "max" interchangeably.

Some of them are in fact max's, I believe. They are complicated :-(.
It might be worth somebody taking two steps back and seeing if we need
quite so many knobs. I think we got here partly by not wanting to
predetermine vacuuming strategies, but it doesn't help to offer
flexibility if people can't figure out how to use it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-14 18:40:50 Re: Wisconsin benchmark
Previous Message Neil Best 2009-08-14 18:31:44 Re: [HACKERS] \copy: unexpected response (4)

Browse pgsql-performance by date

  From Date Subject
Next Message Reid Thompson 2009-08-14 19:43:04 Re: Memory reporting on CentOS Linux
Previous Message Jeremy Carroll 2009-08-14 18:00:44 Memory reporting on CentOS Linux