Re: Large shared_buffer stalls WAS: proposal: Set effective_cache_size to greater of .conf value, shared_buffers

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Large shared_buffer stalls WAS: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Date: 2013-09-13 20:26:47
Message-ID: 52337507.4050409@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/13/2013 01:25 PM, Andres Freund wrote:
>
>
> Josh Berkus <josh(at)agliodbs(dot)com> schrieb:
>
>> What's notable is that sometimes it's just *one* of the replicas which
>> goes into paralysis. If the master gets this issue though, the
>> replicas
>> experience it soon afterwards. Increasing wal_buffers from 16GB to
>> 64GB
>> seems to make this issue happen less frequently, but it doesn't go away
>> entirely.
>
> Youre talking about MB, not GB here, right?

Oh, yes, right.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2013-09-13 20:40:54 Completing PL support for Event Triggers
Previous Message Andres Freund 2013-09-13 20:25:39 Re: Large shared_buffer stalls WAS: proposal: Set effective_cache_size to greater of .conf value, shared_buffers