Re: Double entries in log for page slots in beta3

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Double entries in log for page slots in beta3
Date: 2006-11-28 22:03:52
Message-ID: 200611282203.kASM3qT22061@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner wrote:
> > If there's a better way for me to be managing this, let me know
> > and I'll happily withdraw my requests that the message be spewed
> > twice.
>
> I've generally been capturing the output of my nightly VACUUM ANALYZE
> VERBOSE run, and looking for this information at the end of that file.
>
> > the only reason I
> > still have a scheduled database- wide- vacuum is for this FSM
> message.
>
> Isn't it necessary to do this periodically to prevent transaction ID
> wraparound?

autovacuum takes care of that too, at least in 8.2 and I think 8.1.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2006-11-28 22:51:09 Re: [HACKERS] pg_dump -t broken for mixed case table names in beta3?
Previous Message Bruce Momjian 2006-11-28 21:51:25 Re: [COMMITTERS] pgsql: Fix some translator comments so that