Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Date
Msg-id CAB7nPqTE4n8v3z1PdWirSj9F4t-opTexjtqv1HRJC38Tug=C1w@mail.gmail.com
Whole thread Raw
In response to [HACKERS] segment size depending *_wal_size defaults (was increasing thedefault WAL segment size)  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Andres Freund
Date:
Subject: [HACKERS] segment size depending *_wal_size defaults (was increasing thedefault WAL segment size)
Next
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] A design for amcheck heapam verification