| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | George Wilk <gwilk(at)ellacoya(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: checkpoint_timeout irrelevant in 8.1.9 |
| Date: | 2007-06-20 17:45:55 |
| Message-ID: | 467967D3.9070001@commandprompt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
George Wilk wrote:
> 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.
>
There is no such thing as checkpoint creation. Checkpoint timeout means
that at 30 seconds (based on checkpoint_timeout) it will checkpoint
unless it needs to do so sooner.
Joshua D. Drake
>
>
> This is not satisfactory in a low transaction volume environment. Any
> hints on how else can I trigger checkpoint?
>
>
>
> Thanks in advance,
>
>
>
> ~george
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-20 17:56:29 | Re: checkpoint_timeout irrelevant in 8.1.9 |
| Previous Message | George Wilk | 2007-06-20 17:26:34 | checkpoint_timeout irrelevant in 8.1.9 |