| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | otar shavadze <oshavadze(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file |
| Date: | 2016-10-03 19:46:20 |
| Message-ID: | 11310.1475523980@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
otar shavadze <oshavadze(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-03 20:01:03 | Re: Problems with pg_upgrade after change of unix user running db. |
| Previous Message | otar shavadze | 2016-10-03 19:05:18 | Understanding “max_wal_size” and “min_wal_size” parameters default values from postgresql.conf file |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-10-03 19:50:28 | Re: "Re: Question about grant create on database and pg_dump/pg_dumpall |
| Previous Message | Robert Haas | 2016-10-03 19:43:33 | Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation. |