Thread: How do I find out where this warning is coming from?

Rob Richardson <RDRichardson@rad-con.com> writes:
> I've get several processes running that use the same database.  My database log file is filled with these:
> 2014-04-09 14:16:45 EDT WARNING:  invalid value for parameter "search_path": "public, operationsplanning,
cooling_stands"
> 2014-04-09 14:16:45 EDT DETAIL:  schema "cooling_stands" does not exist

> I would like to have more information in the file about this, such as
> the source process or the statement that is throwing this warning.

Since there's not a statement there already, I'd imagine this is coming
from connection-time processing of values installed by ALTER USER SET
or ALTER DATABASE SET.  A look into the relevant system catalogs should
find the bogus setting.  Or you could turn on log_connections to get
some info about what's making the connection that throws the warning.
(I'd suggest adding %p to your log_line_prefix so you can definitively
connect this message with the connection log one ...)

            regards, tom lane

I’ve get several processes running that use the same database.  My database log file is filled with these:

2014-04-09 14:16:45 EDT WARNING:  invalid value for parameter "search_path": "public, operationsplanning, cooling_stands"

2014-04-09 14:16:45 EDT DETAIL:  schema "cooling_stands" does not exist

 

I would like to have more information in the file about this, such as the source process or the statement that is throwing this warning.  For now, all I have to go on is that the error shows up once a minute.  I didn’t see anything in postgresql.conf to control the format of this message, but there could well be something I didn’t understand.

-- 
Vik