Re: FATAL: database "a/system_data" does not exist - Mailing list pgsql-general

I put the log_statement to 'all'  and log_connections  too.
I get below
May 14 09:18:45 LOG:  execute <unnamed>: SELECT gid FROM pg_prepared_xacts
May 14 09:18:45 LOG:  connection received: host=127.0.0.1 port=55618
May 14 09:18:45 LOG:  connection authorized: user=postgres
database=a/system_data
May 14 09:18:45 FATAL:  database "a/system_data" does not exist


Do you think defining search_path for postgres user role do the trick.
Will search_path lead to any other issue?



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/FATAL-database-a-system-data-does-not-exist-tp5754839p5755384.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.