Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
In postgres 11.5 for a running session suddenly lot of errors reported in pg_logs "relation does not exist". After enabling extra logging we have found out that just before the errors the following statement is getting executed and feels same is the culprit.
SELECT pg_catalog.set_config('search_path', '', false)
We are not running it. Could anyone please help me to understand by whom and under what circumstances it is getting executed.
Let me pull out my crystal ball and see what you did...
Ah! I see you restoring a plain format pg_dump from an interactive session using \i dumpfile, so that the settings from the dump remain active in your session after the restore is completed.
RESET search_path; or - simpler - disconnect and reconnect. Settings changed with SET only hold for the duration of a database session.
Nov 20, 2020 at 7:56
pg_dump and pg_restore are not SQL statements, they are not run in the database. pg_dump produces a file that contains the statement in your question. You run that file with \i, so the statement shows up in your log. Nothing to worry. Just disconnect and reconnect, and you are good.
Nov 20, 2020 at 8:15
After looking at the source code of Postgres I have found that libpqconnect is running it while making a connection. There are many places but libpqconnect is the file where pg_is_in_reovery is also running after the search path and satisfying the my criteria.