From: George Wilk <gwilk@ellacoya.com>
To: pgsql-admin@postgresql.org
Subject: checkpoint_timeout irrelevant in 8.1.9
Date: Wed, 20 Jun 2007 13:26:34 -0400
Message-ID: <002501c7b360$267ac1c0$0d7ba8c0@ellacoya.com> (raw)
According to the WAL config documentation correctly, checkpoints are created
every
<mk:@MSITStore:C:\Program%20Files\PostgreSQL\8.2\pgAdmin%20III\docs\en_US\pg
admin3.chm::/pg/runtime-config-wal.html#guc-checkpoint-segments>
checkpoint_segments log segments, or every
<mk:@MSITStore:C:\Program%20Files\PostgreSQL\8.2\pgAdmin%20III\docs\en_US\pg
admin3.chm::/pg/runtime-config-wal.html#guc-checkpoint-timeout>
checkpoint_timeout seconds, whichever comes first. However, it seems as
though setting my checkpoint_timeout has no effect on checkpoint creation (
I have it set to 30 seconds). Forcing checkpoint by running psql -c
CHECKPOINT mydb doesn't do the trick either. Checkpoints are created solely
based on the checkpoint_segments logs reaching their configured size.
This is not satisfactory in a low transaction volume environment. Any hints
on how else can I trigger checkpoint?
Thanks in advance,
~george
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gwilk@ellacoya.com
Subject: Re: checkpoint_timeout irrelevant in 8.1.9
In-Reply-To: <002501c7b360$267ac1c0$0d7ba8c0@ellacoya.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox