X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E1A72D1D31D for ; Fri, 6 Feb 2004 15:33:06 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 43488-10 for ; Fri, 6 Feb 2004 11:33:06 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 3EC5FD1D332 for ; Fri, 6 Feb 2004 11:33:02 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i16FX6lp029987; Fri, 6 Feb 2004 10:33:06 -0500 (EST) To: Shane Wright Cc: pgsql-admin@postgresql.org Subject: Re: hanging for 30sec when checkpointing In-reply-to: <56DEF96A-5888-11D8-85B9-000393A5890E@shanewright.co.uk> References: <40202216.4010608@shanewright.co.uk> <56DEF96A-5888-11D8-85B9-000393A5890E@shanewright.co.uk> Comments: In-reply-to Shane Wright message dated "Fri, 06 Feb 2004 09:39:20 +0000" Date: Fri, 06 Feb 2004 10:33:06 -0500 Message-ID: <29986.1076081586@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/77 X-Sequence-Number: 12251 Shane Wright writes: > Hmm that gives me an idea, for bulk processing, is there a way of > detecting from a client when a checkpoint is about to happen so it can > wait until it's finished? No, but maybe you could think about scheduling checkpoints yourself to not coincide with your bulk jobs. You could issue CHECKPOINT commands from cron or whatever is dispatching your bulk jobs, and then widen the checkpoint-timing parameters in postgresql.conf enough to avoid automatic CHECKPOINTs. The only real drawback of less-frequent CHECKPOINTs is that the amount of WAL space required goes up proportionally. (Oh, and it might take proportionally longer to recover after a crash, too.) regards, tom lane