On Fri, Oct 18, 2013 at 2:01 PM, Jayadevan M wrote:
> Thanks. This is what I have. May be it is not really an error?
>
> 2013-10-18 12:23:54.996 IST,,,8855,,523c23ea.2297,20,,2013-09-20 16:01:06
> IST,,0,LOG,0,"received SIGHUP, reloading configuration files",""
> 2013-10-18 12:23:54.99
Thanks. This is what I have. May be it is not really an error?
2013-10-18 12:23:54.996 IST,,,8855,,523c23ea.2297,20,,2013-09-20 16:01:06
IST,,0,LOG,0,"received SIGHUP, reloading configuration files",""
2013-10-18 12:23:54.996 IST,,,8855,,523c23ea.2297,21,,2013-09-20 16:01:06
IST,,0,LOG
Jayadevan M writes:
> Which is the quickest way to troubleshot the message "
> LOG: configuration file "/postgresql.conf" contains errors;
> unaffected changes were applied"" ?
There should be log message(s) before that one complaining about the
specific problems.
re
Hi,
Which is the quickest way to troubleshot the message "
LOG: configuration file "/postgresql.conf" contains errors;
unaffected changes were applied"" ?
I made a couple of changes a few days ago, and did not reload Today I made
some more changes and did a pg_ctl reload.
Is there an optio
