Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size)

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Beena Emerson <memissemerson(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size)
Date: 2017-08-30 02:20:30
Message-ID: b4570985-a4dd-98ae-c7f9-539d5e9c6275@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/29/17 20:36, Andres Freund wrote:
> So the question is whether we want {max,min}_wal_size be sized in
> multiples of segment sizes or as a proper byte size. I'm leaning
> towards the latter.

I'm not sure what the question is or what its impact would be.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-08-30 02:22:21 Re: A design for amcheck heapam verification
Previous Message Michael Paquier 2017-08-30 01:44:54 Re: Update low-level backup documentation to match actual behavior