Re: Logging behavior not changing on reload

Hmm, usually when you do a pg_ctl reload, the log files has entries of that
event plus changes in parameter values. Check you PostgreSQL log file? May
be do a tail -f on it and try pg_ctl reload once again?

On Wed, Apr 2, 2014 at 7:09 PM, Matthew Foster - NOAA Federal <
matthew(dot)foster(at)noaa(dot)gov> wrote:

> Thank you for the quick reply. SHOW indeed indicates that the parameters
> have not actually changed. I guess my next question is: Why did they not
> change on reload?
>
> Matt
>
>
>
> On Wed, Apr 2, 2014 at 8:29 AM, Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com>wrote:
>
>> You could try show command (
>> http://www.postgresql.org/docs/9.3/static/sql-show.html) and see if the
>> changes have taken effect. Usually there are comments against each
>> parameter which mention if a restart is required. Example,
>> port = 5432 # (change requires restart)
>>
>>
>> On Wed, Apr 2, 2014 at 6:36 PM, Matthew Foster - NOAA Federal <
>> matthew(dot)foster(at)noaa(dot)gov> wrote:
>>
>>> I changed a few logging parameters on our 9.1 server (e.g.
>>> log_rotation_age, log_rotation_size, log_min_messages). After a reload,
>>> the logging behavior has not changed. Is a restart required for these?
>>> The documentation doesn't indicate that it is.
>>>
>>> Thanks.
>>>
>>> Matt
>>>
>>>
>>
>