| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Gourish Singbal <gourish(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Autovacuuming |
| Date: | 2006-04-24 21:36:56 |
| Message-ID: | 6697.1145914616@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Jim C. Nasby wrote:
>> Ok, I'll bite... any idea how (MaxTransactionId >> 3) * 3 was chosen? I
>> don't see anything about it in vacuum.c...
> I don't remember exactly why was that constant chosen. IIRC Tom pulled
> it out of thin air.
Pretty much. One of the main constraints at the time was that we wanted
it to be warning for a good long time before actual wraparound happened,
because the consequences would be so catastrophic. Now that there's
some failsafe code in place, it might be reasonable to narrow the margin
so it doesn't start bleating quite so soon. We'd still be pulling
specific numbers out of the air though ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandre Leclerc | 2006-04-24 21:37:04 | moving /data folder (win32, pgsql 8.1.3) |
| Previous Message | Bruno Wolff III | 2006-04-24 19:10:09 | Re: dblink not working in FC5 (Solved) |