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 Andres Freund
Subject Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Date
Msg-id 20170830010651.4hazv5d76qp77z67@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)  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Tree view 
On 2017-08-30 09:49:14 +0900, Michael Paquier wrote:
> 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.

No code difficulties here, I think we just need to decide what we want.


> 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.


Greetings,

Andres Freund

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] A design for amcheck heapam verification
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)