| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Michael Paesold <mpaesold(at)gmx(dot)at>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Autovacuum loose ends |
| Date: | 2005-08-01 14:03:59 |
| Message-ID: | 2444.1122905039@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>>> - Xid-wraparound VACUUM is now FULL without ANALYZE
>>
>> Am I right in my assumption that this VACUUM FULL can happen for any
>> database, not just a template database?
> Ah, right. I think it would be OK if we made it FULL only for
> datallowcon=false databases. OTOH maybe it's not worth at all making
> the distinction and we should continue using the previous policy of
> issuing only non-FULL VACUUM.
Strikes me as a waste of cycles: the one database *least* likely to be
in need of a VACUUM FULL is template0.
What we perhaps should consider is VACUUM FREEZE, not FULL, when hitting
a template database --- this would maximize the interval before needing
to do it again.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-08-01 14:04:01 | Re: Remote administration functionality |
| Previous Message | Bruce Momjian | 2005-08-01 14:02:41 | Re: Remote administration functionality |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2005-08-01 14:05:15 | Re: [HACKERS] For review: Server instrumentation patch |
| Previous Message | Dave Page | 2005-08-01 13:54:38 | Re: [HACKERS] For review: Server instrumentation patch |