| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <alvherre(at)commandprompt(dot)com>,<duanlg(at)nec-as(dot)nec(dot)com(dot)cn>, <pgsql-performance(at)postgresql(dot)org>, "Matt Smiley" <mss(at)rentrak(dot)com> |
| Subject: | Re: too many clog files |
| Date: | 2008-09-10 17:47:54 |
| Message-ID: | 48C7C1FA.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The expected behavior (in 8.2 and newer) is to maintain about
> autovacuum_freeze_max_age transactions' worth of clog; which is to
say
> about 50MB at the default settings.
The active database I checked, where it didn't go all the way back to
0000, had 50 MB of files; so I guess it is working as intended.
It sounds like the advice to the OP that running VACUUM FREEZE on all
databases to clean up the files was off base?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2008-09-10 17:49:22 | Re: Improve COPY performance for large data sets |
| Previous Message | Tom Lane | 2008-09-10 17:42:40 | Re: too many clog files |