From: | "George Wilk" <gwilk(at)ellacoya(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | checkpoint_timeout irrelevant in 8.1.9 |
Date: | 2007-06-20 17:26:34 |
Message-ID: | 002501c7b360$267ac1c0$0d7ba8c0@ellacoya.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-06-20 17:45:55 | Re: checkpoint_timeout irrelevant in 8.1.9 |
Previous Message | Sibte Abbas | 2007-06-20 17:19:24 | Re: Logging autovacuum activity |