Re: Patch: raise default for max_wal_segments to 1GB

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Venkata Balaji N <nag1010(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Patch: raise default for max_wal_segments to 1GB
Date: 2015-03-02 23:40:27
Message-ID: 54F4F4EB.7030401@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/02/2015 03:18 PM, Josh Berkus wrote:
> Attached.
>
> Per discussion on the thread "Redesigning checkpoint_segments" this
> raises the default for the new parameter "max_wal_size" to 1GB.
>
> Seems too small to add it to the CF, but if you want me to, I will.

Ooops, patch didn't include the docs update for some reason. Fixed.

Also, link to relevant post:

http://www.postgresql.org/message-id/54F4EF49.1010002@agliodbs.com

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

Attachment Content-Type Size
max_wal_1gb_b.patch text/x-patch 2.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-03-02 23:43:33 Re: Patch: raise default for max_wal_segments to 1GB
Previous Message Jim Nasby 2015-03-02 23:39:44 Re: Proposal: knowing detail of config files via SQL