Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3A5879FBF53 for ; Wed, 20 Jun 2007 14:57:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 47896-03 for ; Wed, 20 Jun 2007 14:57:21 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id EA99E9FBF8F for ; Wed, 20 Jun 2007 14:57:19 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-13-143-52.bk13-dsl.surnet.cl [190.13.143.52]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l5KHuYZl011206; Wed, 20 Jun 2007 10:56:46 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1345C32A2C; Wed, 20 Jun 2007 13:56:29 -0400 (CLT) Date: Wed, 20 Jun 2007 13:56:29 -0400 From: Alvaro Herrera To: George Wilk Cc: pgsql-admin@postgresql.org Subject: Re: checkpoint_timeout irrelevant in 8.1.9 Message-ID: <20070620175629.GO30369@alvh.no-ip.org> References: <002501c7b360$267ac1c0$0d7ba8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <002501c7b360$267ac1c0$0d7ba8c0@ellacoya.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 20 Jun 2007 10:56:48 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/206 X-Sequence-Number: 25874 George Wilk wrote: > According to the WAL config documentation correctly, checkpoints are created > every > admin3.chm::/pg/runtime-config-wal.html#guc-checkpoint-segments> > checkpoint_segments log segments, or every > 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. You are misunderstand what a checkpoint is. Also, why would you need a checkpoint every 30 seconds escapes me. What you probably want is to archive the WAL segment currently in use. There's a function you can use for that, pg_switch_xlog(). -- Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 18.1", W 73º 13' 56.4" "In Europe they call me Niklaus Wirth; in the US they call me Nickel's worth. That's because in Europe they call me by name, and in the US by value!"