Re: archive_timeout, checkpoint_timeout

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rob Adams <robfadams(at)cox(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: archive_timeout, checkpoint_timeout
Date: 2008-07-31 01:25:38
Message-ID: 26703.1217467538@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Rob Adams <robfadams(at)cox(dot)net> writes:
> archive_timeout only seems to work if it's >= checkpoint_timeout.

Hmm, no, they should be pretty independent. Define "seems to work"
please?

One possible connection is that an xlog file switch will not actually
happen unless some xlog output has been generated since the last switch.
If you were watching an otherwise-idle system then maybe the checkpoint
records are needed to make it look like a switch is needed. OTOH if
it's *that* idle then the checkpoints should be no-ops too. So we
need a bit more context to understand what's happening. How often
do real updates happen on your database?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rob Adams 2008-07-31 02:25:45 Re: archive_timeout, checkpoint_timeout
Previous Message Craig Ringer 2008-07-31 01:15:05 Re: Connecting to an existing transaction state.