Re: [HACKERS] WAL archiving idle database - Mailing list pgsql-general

From Jeff Davis
Subject Re: [HACKERS] WAL archiving idle database
Date
Msg-id 1193441286.7624.117.camel@dogma.ljc.laika.com
Whole thread Raw
In response to Re: WAL archiving idle database  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] WAL archiving idle database  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-general
On Fri, 2007-10-26 at 18:47 -0400, Tom Lane wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
> > What's happening is that you have a checkpoint_timeout of 5 minutes, and
> > that checkpoint must write a checkpoint record in the WAL, prompting the
> > archiving.
>
> > If you want it to happen less frequently, it's often safe to have
> > checkpoint timeout set to something larger by a reasonable amount.
>
> I think you're confusing checkpoint_timeout and archive_timeout...

Thanks for clarifying it. The user-visible behavior, as I understand it,
is that the time between archiving on an idle database is:
MAX(archive_timeout,checkpoint_timeout)

[ of course, there's no guarantee that the archive_command succeeds in
that time ]

It looks like checkpoint_timeout was the limiting factor, in his case.

Regards,
    Jeff Davis


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] WAL archiving idle database
Next
From: Jeff Davis
Date:
Subject: Re: [HACKERS] WAL archiving idle database