Customized Options Threshold Error

From: <furuyao(at)pm(dot)nttdata(dot)co(dot)jp>
To: <pgsql-hackers(at)postgresql(dot)org>
Cc: <teranishih(at)nttdata(dot)co(dot)jp>
Subject: Customized Options Threshold Error
Date: 2014-11-14 08:00:05
Message-ID: A9C510524E235E44AE909CD4027AE196BF7D6FB273@MBX-MSG-SV03.msg.nttdata.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

When we specify a value which exceeds valid range in "Customized Options" ,
its behavior is different from "Parameter Interaction via Configuration File" behavior.

In case of "Parameter Interaction via Configuration File", it finish with FATAL error when it get threshold error.
But in "Customized Options", it just printout WARNING and continue the process with default value.

In manual, it says "issue warnings for any unrecognized placeholders that begin with its extension name" written in "18.16. Customized Options".
So when extension name is correct and the value exceeds the threshold range,
I think it should end with FATAL error just like "Parameter Interaction via Configuration File".
Thought?

Following is the threshold error log. One is "Customized Options Threshold Error" and another is "Parameter Interaction via Configuration File Threshold Error".

"Customized Options Threshold Error"

WARNING: invalid value for parameter "pg_receivexlog_mng.monitor_interval": "2147483648"
HINT: Value exceeds integer range.
LOG: registering background worker "pg_receivexlog_mng"

"Parameter Interaction via Configuration File Threshold Error"

FATAL: configuration file "/dbfp/data/postgresql.conf" contains errors

Regards,

--
Furuya Osamu

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2014-11-14 08:04:00 Re: REINDEX CONCURRENTLY 2.0
Previous Message Amit Kapila 2014-11-14 07:55:04 Re: pg_basebackup vs. Windows and tablespaces