Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 26C559FB569 for ; Wed, 20 Jun 2007 14:26:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 27876-01 for ; Wed, 20 Jun 2007 14:26:39 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 8A65F9FBEDF for ; Wed, 20 Jun 2007 14:26:40 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by svr4.postgresql.org (Postfix) with ESMTP id 23D8A5AF028 for ; Wed, 20 Jun 2007 17:26:39 +0000 (GMT) Received: from YZANGXP ([192.168.123.13]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 13:26:36 -0400 From: "George Wilk" To: Subject: checkpoint_timeout irrelevant in 8.1.9 Date: Wed, 20 Jun 2007 13:26:34 -0400 Message-ID: <002501c7b360$267ac1c0$0d7ba8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C7B33E.9F6921C0" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcezYCZUlpMUo7S2T3ClIGokxgdtmA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-OriginalArrivalTime: 20 Jun 2007 17:26:36.0972 (UTC) FILETIME=[27D2FEC0:01C7B360] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-3.800.1026-15250.000 X-TM-AS-Result: No--16.243000-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.137 tagged_above=0 required=5 tests=BAYES_50=0.001, FORGED_RCVD_HELO=0.135, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200706/204 X-Sequence-Number: 25872 This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C7B33E.9F6921C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit According to the WAL config documentation correctly, checkpoints are created every checkpoint_segments log segments, or every 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 ------=_NextPart_000_0026_01C7B33E.9F6921C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

According to the WAL config documentation correctly, = checkpoints are created every 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

------=_NextPart_000_0026_01C7B33E.9F6921C0--