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

From Andres Freund
Subject Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Date
Msg-id 20170830011609.3dk67tixa4ryq3io@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
List pgsql-hackers
On 2017-08-30 10:14:22 +0900, Michael Paquier wrote:
> 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.

I'm doubtfull of that. But even if, it'd not be hard to GUC support.

- Andres



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Update low-level backup documentation to match actual behavior