| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Duan Ligong <duanlg(at)nec-as(dot)nec(dot)com(dot)cn>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: too many clog files |
| Date: | 2008-09-02 05:47:01 |
| Message-ID: | 6128.1220334421@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Tue, 2 Sep 2008, Duan Ligong wrote:
>> - Can we controll the maximum number of the clog files?
> The reference Alvaro suggested at
> http://www.postgresql.org/docs/8.3/interactive/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
> goes over that. If you reduce autovacuum_freeze_max_age, that reduces the
> expected maximum size of the clog files.
Duan's first post stated that he is running 8.1, which I believe had a
quite different rule for truncating pg_clog --- it definitely has not
got the parameter autovacuum_freeze_max_age.
Too tired to go reread the 8.1 code right now, but don't quote 8.3
docs at him, 'cause they're not too relevant.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Finneid | 2008-09-02 06:39:24 | Re: slow update of index during insert/copy |
| Previous Message | Greg Smith | 2008-09-02 05:32:01 | Re: too many clog files |