Re: Segment best size

From: Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Segment best size
Date: 2013-04-14 03:01:13
Message-ID: CANs8QJaJ32259E8_mYmZmZOxEjYENmHMhvwEBYw4L4BUK8W_0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sat, Apr 13, 2013 at 4:51 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

> On Sat, Apr 13, 2013 at 10:29 AM, Rodrigo Barboza <rodrigombufrj(at)gmail(dot)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)?

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2013-04-14 05:20:56 Re: Segment best size
Previous Message Jeff Janes 2013-04-13 20:54:22 Re: slow bitmap heap scans on pg 9.2