Re: [GENERAL] Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file - Mailing list pgsql-general

From otar shavadze
Subject Re: [GENERAL] Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file
Date
Msg-id CAG-jOyD3KrEbWvDL1cnVffho+dGgUvwhHL8p3uTU0zBWKzFnPQ@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL]Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thank you very much

On Mon, Oct 3, 2016 at 11:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
otar shavadze <oshavadze@gmail.com> writes:
> 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.

They do match the defaults.

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

The problem seems to be that somebody missed out adding GUC_UNIT_XSEGS
to the switch in GetConfigOptionByNum.  It should be showing you
something like "16MB" in the unit column, I think.

                        regards, tom lane

pgsql-general by date:

Previous
From: Raymond O'Donnell
Date:
Subject: Re: isnull() function in pgAdmin3
Next
From: "David G. Johnston"
Date:
Subject: Re: isnull() function in pgAdmin3