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.
On Wed, Oct 8, 2008 at 8:31 AM, Rafael Domiciano <rafael(dot)domiciano(at)gmail(dot)com
> 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.
> Rafael Domiciano
> Postgres DBA
> 2008/10/7 <chirag(dot)dave(at)gmail(dot)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(dot)domiciano(at)gmail(dot)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
>>> Rafael Domiciano
In response to
pgsql-admin by date
|Next:||From: Brad Nicholson||Date: 2008-10-08 14:23:00|
|Subject: Re: checkpoint_timeout|
|Previous:||From: Rafael Domiciano||Date: 2008-10-08 13:40:29|
|Subject: Re: Shared_buffers hint|