Re: pgsql: Make WAL segment size configurable at initdb time. - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Make WAL segment size configurable at initdb time.
Date
Msg-id 20180921045316.GI1338@paquier.xyz
Whole thread Raw
In response to Re: pgsql: Make WAL segment size configurable at initdb time.  (Andres Freund <andres@anarazel.de>)
Responses Re: pgsql: Make WAL segment size configurable at initdb time.  (David Steele <david@pgmasters.net>)
List pgsql-committers
On Thu, Sep 20, 2018 at 06:23:54PM -0700, Andres Freund wrote:
> 16*M*B, right?  If so, that's normal - pg_settings just reports the
> values in the underlying unit - which is XLOG_BLCKSZ, compile-time
> defaulting to 8KB. 8192 * 2048 = 16MB.  That's the same in various other
> settings.

Would it bring less confusion if we append something like "When querying
pg_settings"?  I can see David's point the current phrasing is
confusing: we don't know if this comes from pg_settings or from SHOW.
It obviously refers to the former, but one can understand that it refers
to the latter.

A second parameter in config.sgml where this formulation is used is
segment_size.
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: pgsql: Error out for clang on x86-32 without SSE2 support,no -fexcess-
Next
From: Michael Paquier
Date:
Subject: pgsql: Document lock taken on referenced table when adding a foreignke