Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3B7C037BA5B for ; Wed, 8 Oct 2008 11:15:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 46964-04 for ; Wed, 8 Oct 2008 11:15:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by postgresql.org (Postfix) with ESMTP id 9E6BE37BA28 for ; Wed, 8 Oct 2008 11:15:34 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so3938043rvf.43 for ; Wed, 08 Oct 2008 07:15:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=Zwm6TxDUjMlh8GfYFbW+vpQlPikQtLEn2PtG3WaWvx8=; b=aaSkE8GPFBoX6wWhVp6xJf4U0yCv2YKVLInLV13rJaqWPoe9zgo+RvYxWkREM1Kh39 4LCWFg/5cNztEKvin+/wMNz1Oio7S8mePLnrDfOJYpBjqi4uXhxRqG8ruBOYrLx5h6tE IuqNx7XMfi0TDacfzgmEoxsgyqu5kmM6msDk0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=MECTmyemUwvXtZGDST9pzW+hqbkZyOZ/HJYhM+SESk3LsBB/+AGq2CjcHDdA35vRpk 0kj+eYkf9KsPHeDpTR1jk2U7uI7oNarLaJBNlZ3p3jNrRtl3NObUgKN/PHeRX1wrybu6 hrgR/2HdeZnoX3CAJGc16hXdZCPCgnDERb5gk= Received: by 10.141.34.12 with SMTP id m12mr4974230rvj.26.1223475332542; Wed, 08 Oct 2008 07:15:32 -0700 (PDT) Received: by 10.141.43.10 with HTTP; Wed, 8 Oct 2008 07:15:32 -0700 (PDT) Message-ID: Date: Wed, 8 Oct 2008 10:15:32 -0400 From: chirag.dave@gmail.com To: "Rafael Domiciano" Subject: Re: checkpoint_timeout Cc: "pgsql-admin@postgresql.org" In-Reply-To: <3a0028490810080531y155edffi7ff7c68b965a834a@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_55181_27827330.1223475332534" References: <3a0028490810071321j32b4f450m95123d02b9fe6f49@mail.gmail.com> <3a0028490810080531y155edffi7ff7c68b965a834a@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200810/48 X-Sequence-Number: 30504 ------=_Part_55181_27827330.1223475332534 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Again very little information to work with but I would start with looking at postgres logs. you should enable checkpoint_timeout to a very high number, so you have an entry in the log anytime checkpoint occurs and set your log_min_duration_statement to number which your considered to be long running, to log all slower statement. Chirag Dave DBA, Afilias On Wed, Oct 8, 2008 at 8:31 AM, Rafael Domiciano wrote: > The server is running Postgres 8.2.4When the server is doing too much > operations like I, U or D the postgres stop a while each 5 min...! > I mean "stopping" that I don't receive any response from postgres, and the > process the all people are running stay there, waiting for something. > I read a several names to it like: gap, stall, slowdown... I don't know the > write expression for this situation. > > I hope you can help me. > > Thnks, > > Rafael Domiciano > Postgres DBA > > 2008/10/7 > > What version of postgres are you running ? and please also provide more >> information about your suspected slowdown ? >> >> >> >> >> >> On Tue, Oct 7, 2008 at 4:21 PM, Rafael Domiciano < >> rafael.domiciano@gmail.com> wrote: >> >>> Hello there, >>> I'm having some slowndowns in my postgresql server, and I had been >>> reading something about checkpoints, that could resolve my problem. >>> Now, I have: >>> checkpoint_segments = 30 # in logfile segments, min 1, >>> 16MB each >>> #checkpoint_timeout = 5min >>> >>> And I percebed that this slowndown is occuring for 5 min...! So I'm >>> suposing that the problem is in the checkpoint_timeout. >>> >>> What's the impact to chang it to: >>> checkpoint_timeout = 2min or >>> checkpoint_timeout = 5min >>> >>> Tnhks, >>> >>> Rafael Domiciano >>> >> >> > ------=_Part_55181_27827330.1223475332534 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Again very little information to work with but I would start with looking at postgres logs. you should enable checkpoint_timeout to a very high number, so you have an entry in the log anytime checkpoint occurs and set your log_min_duration_statement to number which your considered to be long running, to log all slower statement.

Chirag Dave
DBA, Afilias

On Wed, Oct 8, 2008 at 8:31 AM, Rafael Domiciano <rafael.domiciano@gmail.com> wrote:
The server is running Postgres 8.2.4
When the server is doing too much operations like I, U or D the postgres stop a while each 5 min...!
I mean "stopping" that I don't receive any response from postgres, and the process the all people are running stay there, waiting for something.
I read a several names to it like: gap, stall, slowdown... I don't know the write expression for this situation.

I hope you can help me.

Thnks,

Rafael Domiciano
Postgres DBA

2008/10/7 <chirag.dave@gmail.com>

What version of postgres are you running ?  and please also provide more information about your suspected slowdown ?





On Tue, Oct 7, 2008 at 4:21 PM, Rafael Domiciano <rafael.domiciano@gmail.com> wrote:
Hello there,

I'm having some slowndowns in my postgresql server, and I had been reading something about checkpoints, that could resolve my problem.
Now, I have:
checkpoint_segments = 30                # in logfile segments, min 1, 16MB each
#checkpoint_timeout = 5min 

And I percebed that this slowndown is occuring for 5 min...! So I'm suposing that the problem is in the checkpoint_timeout.

What's the impact to chang it to:
checkpoint_timeout = 2min or
checkpoint_timeout = 5min

Tnhks,

Rafael Domiciano



------=_Part_55181_27827330.1223475332534--