Re: Segment best size - Mailing list pgsql-performance

From Rodrigo Barboza
Subject Re: Segment best size
Date
Msg-id CANs8QJaJ32259E8_mYmZmZOxEjYENmHMhvwEBYw4L4BUK8W_0Q@mail.gmail.com
Whole thread Raw
In response to Re: Segment best size  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Segment best size  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: Segment best size  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-performance



On Sat, Apr 13, 2013 at 4:51 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
On Sat, Apr 13, 2013 at 10:29 AM, Rodrigo Barboza <rodrigombufrj@gmail.com> wrote:


I was receiving warning messages of pgstat timeout.
I started looking for the solution for this problem and this doubt came out.
But it doesn't seem to be the problem.

Usually that just means that you are dirtying pages faster than your hard drives can write them out, leading to IO contention.  Sometimes you can do something about this by changing the work-load to dirty pages in more compact regions, or by changing the configuration.  Often the only effective thing you can do is buy more hard-drives.

Cheers,

Jeff


Would it help if I changed the checkpoint_completion_target to something close to 0.7 (mine is the default 0.5) or raise the checkpoint_segments (it is 32 now)?

pgsql-performance by date:

Previous
From: Rikard Pavelic
Date:
Subject: Re: limit is sometimes not pushed in view with order
Next
From: Scott Marlowe
Date:
Subject: Re: Segment best size