Re: Incorrectly reporting config errors

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Incorrectly reporting config errors
Дата
Msg-id 31689.1390329355@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Incorrectly reporting config errors  (Thom Brown <thom@linux.com>)
Ответы Re: Incorrectly reporting config errors  (Thom Brown <thom@linux.com>)
Список pgsql-hackers
Thom Brown <thom@linux.com> writes:
> I'm getting a report of a config error when changing a config value
> that requires a restart:
> ...
> 2014-01-21 18:14:53 GMT [28718]: [4-1] user=,db=,client= LOG:
> received SIGHUP, reloading configuration files
> 2014-01-21 18:14:53 GMT [28718]: [5-1] user=,db=,client= LOG:
> parameter "max_connections" cannot be changed without restarting the
> server
> 2014-01-21 18:14:53 GMT [28718]: [6-1] user=,db=,client= LOG:
> configuration file "/home/thom/Development/data/postgresql.conf"
> contains errors; unaffected changes were applied

> It doesn't contain errors.

Yeah it does: it's got a value that can't be applied.  I think you're
making a semantic quibble.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Bug? could not remove shared memory segment
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: Hard limit on WAL space used (because PANIC sucks)