Skip site navigation (1) Skip section navigation (2)

Re: Proposal: vacuum and autovacuum parameters to control freezing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Subject: Re: Proposal: vacuum and autovacuum parameters to control freezing
Date: 2006-11-05 17:01:54
Message-ID: 15737.1162746114@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
I wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
>> Perhaps you could edit the above if needed?

>         <---- Xids older than freeze_distance will be frozen whenever
>               next visited by VACUUM, but there is no forcing function
>               until they exceed freeze_limit

>> In that case,
>> maybe slightly more differentiated names would be appropriate.

> Got a suggestion?  I think the names *should* be clearly related, but
> as I said, I'm by no means wedded to these particular ones.

After re-reading the above, it strikes me that maybe names based around
"freeze_min" and "freeze_max" would be useful?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-11-05 18:15:24
Subject: Re: [HACKERS] Bug in WAL backup documentation
Previous:From: Tom LaneDate: 2006-11-05 16:49:36
Subject: Re: [HACKERS] Bug in WAL backup documentation

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-11-05 18:15:24
Subject: Re: [HACKERS] Bug in WAL backup documentation
Previous:From: Tom LaneDate: 2006-11-05 16:49:36
Subject: Re: [HACKERS] Bug in WAL backup documentation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group