Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Дата
Msg-id CAB7nPqSP3yv8W09-yzNa4=HDNyRX_w_zL3EcmZoY+9tG8eUOiQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On Wed, Aug 30, 2017 at 11:20 AM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] expanding inheritance in partition bound order
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: [HACKERS] A design for amcheck heapam verification