Thread: postgresql.conf error

postgresql.conf error

From

Jayadevan M

Date:

18 October 2013, 10:07:56

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 option to test the configuration file for errors, after making changes?

Regards,
Jayadevan

Re: postgresql.conf error

From

Tom Lane

Date:

18 October 2013, 10:42:12

Jayadevan M <maymala.jayadevan@gmail.com> 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.

            regards, tom lane

Re: postgresql.conf error

From

Jayadevan M

Date:

18 October 2013, 11:31:52

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,00000,"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,55P02,"parameter ""superuser_reserved_connections"" cannot be changed without restarting the server",,,,,,,,,""
2013-10-18 12:23:54.997 IST,,,8855,,523c23ea.2297,22,,2013-09-20 16:01:06 IST,,0,LOG,F0000,"configuration file ""/pgdata/prod/data_93/postgresql.conf"" contains errors; unaffected changes were applied",,,,,,,,,""

On Fri, Oct 18, 2013 at 1:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Jayadevan M <maymala.jayadevan@gmail.com> 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.

regards, tom lane

Re: postgresql.conf error

From

Raghu Ram

Date:

18 October 2013, 12:00:20

On Fri, Oct 18, 2013 at 2:01 PM, Jayadevan M <maymala.jayadevan@gmail.com> 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,00000,"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,55P02,"parameter ""superuser_reserved_connections"" cannot be changed without restarting the server",,,,,,,,,""
2013-10-18 12:23:54.997 IST,,,8855,,523c23ea.2297,22,,2013-09-20 16:01:06 IST,,0,LOG,F0000,"configuration file ""/pgdata/prod/data_93/postgresql.conf"" contains errors; unaffected changes were applied",,,,,,,,,""

To effect new changes related to "superuser_reserved_connections" parameters in Postgresql.conf file requires RESTART of the PostgreSQL Service.

Thanks & Regards

Raghu Ram