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 CAB7nPqTE4n8v3z1PdWirSj9F4t-opTexjtqv1HRJC38Tug=C1w@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] segment size depending *_wal_size defaults (was increasing thedefault WAL segment size)  (Andres Freund <andres@anarazel.de>)
Ответы 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 9:36 AM, Andres Freund <andres@anarazel.de> 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.

Logically in the code it is just a matter of adjusting multipliers. Do
you think that we should worry about wal segment sizes higher than
2GB? Support for int64 GUCs is not here yet.
-- 
Michael

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: [HACKERS] segment size depending *_wal_size defaults (was increasing thedefault WAL segment size)
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: [HACKERS] A design for amcheck heapam verification