| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Make WAL segment size configurable at initdb time. |
| Date: | 2018-09-21 04:53:16 |
| Message-ID: | 20180921045316.GI1338@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-09-21 06:12:48 | pgsql: Document lock taken on referenced table when adding a foreign ke |
| Previous Message | Andres Freund | 2018-09-21 01:29:38 | pgsql: Error out for clang on x86-32 without SSE2 support, no -fexcess- |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-09-21 04:55:36 | Re: transction_timestamp() inside of procedures |
| Previous Message | Andres Freund | 2018-09-21 04:52:18 | Re: Proposal for Signal Detection Refactoring |