Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Beena Emerson <memissemerson(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size)
Date: 2017-08-30 01:06:51
Message-ID: 20170830010651.4hazv5d76qp77z67@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-08-30 09:49:14 +0900, Michael Paquier wrote:
> On Wed, Aug 30, 2017 at 9:36 AM, Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-08-30 01:14:22 Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size)
Previous Message Peter Geoghegan 2017-08-30 01:00:59 Re: A design for amcheck heapam verification