Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file

From: otar shavadze <oshavadze(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file
Date: 2016-10-03 19:05:18
Message-ID: CAG-jOyA=iNFhN+yB4vfvqh688B7Tr5SArbYcFUAjZi=0Exp-Lg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

According to documentation, for "min_wal_size" and "max_wal_size" parameters
<https://www.postgresql.org/docs/9.5/static/runtime-config-wal.html>

default values are:

For max_wal_size: The default is 1 GB

For min_wal_size: The default is 80 MB

Then I look this parameters from my database config:

select name, setting, unit from pg_settings where name in
('min_wal_size', 'max_wal_size')

Gives result:

name | setting | unit----------------------------------
max_wal_size | 64 |
min_wal_size | 5 |

I have 2 questions:

1) Why these values doesn't match default values, which are shown in docs?
I never changed config settings at all.

2) Why unit column is empty/NULL for these parameters? What means 64 and 5
values in this case? MB? GB? or what?

Why this is not like for example work_mem parameter, when everything is
clear:

name | setting | unit----------------------------------
work_mem | 4096 | kB

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-10-03 19:46:20 Re: Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file
Previous Message otar shavadze 2016-10-03 18:52:48

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-10-03 19:19:08 Re: contrib/pg_visibility craps out in assert-enabled builds
Previous Message Andres Freund 2016-10-03 18:56:33 Re: Removing link-time cross-module refs in contrib