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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Beena Emerson <memissemerson(at)gmail(dot)com>, "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 03:52:26
Message-ID: CAB7nPqSP3yv8W09-yzNa4=HDNyRX_w_zL3EcmZoY+9tG8eUOiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 30, 2017 at 11:20 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> 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.

FWIW, I get the question as: do we want the in-memory values of
min/max_wal_size to be calculated in MB (which is now the case) or
just bytes. Andres tends for using bytes.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2017-08-30 03:56:05 Re: A design for amcheck heapam verification
Previous Message Robert Haas 2017-08-30 03:03:34 Re: expanding inheritance in partition bound order