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 CAB7nPqQGwLNWGdTRpcB418ZdAcuCcd5VKDhpVYLOaOsYWXwshQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default 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
On Wed, Aug 30, 2017 at 10:06 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2017-08-30 09:49:14 +0900, Michael Paquier wrote:
>> Do you think that we should worry about wal segment sizes higher than
>> 2GB? Support for int64 GUCs is not here yet.
>
> 1GB will be the limit anyway.

Yeah, but imagine that we'd want to raise that even more up. By using
bytes, int64 GUCs become mandatory, or we'd come back into using MBs
for this parameter, bringing us back to the original implementation.
That's something worth thinking about.
-- 
Michael



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)