From: | "Scott Carey" <scott(at)richrelevance(dot)com> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:55:26 |
Message-ID: | a1ec7d000809101055m54f27647l4e546ec87e14f4c7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
And potentially to tune down the number kept by modifying the appropriate
freeze parameter for 8.1 (I'm not sure of the details), so that it keeps
perhaps 20MB or so rather than 50MB.
On Wed, Sep 10, 2008 at 10:47 AM, Kevin Grittner <
Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> >>> 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
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-09-10 18:03:45 | Re: too many clog files |
Previous Message | Scott Carey | 2008-09-10 17:51:34 | Re: Improve COPY performance for large data sets |