Re: wal_buffers = -1 - Mailing list pgsql-hackers

From Thom Brown
Subject Re: wal_buffers = -1
Date
Msg-id CAA-aLv4i3kigqSVUgksG_buW9cPCcHS0tYG5oB4o19miyJew2A@mail.gmail.com
Whole thread Raw
In response to wal_buffers = -1  (Magnus Hagander <magnus@hagander.net>)
Responses Re: wal_buffers = -1
List pgsql-hackers
On 17 January 2014 13:01, Magnus Hagander <magnus@hagander.net> wrote:
> Is there any real use-case for not setting wal_buffers to -1 these days?
>
> Or should we just remove it and use the -1 behaviour at all times?
>
> IIRC we discussed not keeping it at all when the autotune behavior was
> introduced, but said we wanted to keep it "just in case". If we're not ready
> to remove it, then does that just mean that we need to fix it so we can?

Robert Haas reported that setting it to 32MB can yield a considerable
performance benefit:

http://www.postgresql.org/message-id/CA+TgmobgMv_aaakLoasBt=5iYfi=kdcOUz0X9TdYe0c2SZ=2Pg@mail.gmail.com

-- 
Thom



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: wal_buffers = -1
Next
From: Andres Freund
Date:
Subject: Re: wal_buffers = -1