BUG #15993: "CREATE OR REPLACE FUNCTION" does not clear search_path - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #15993: "CREATE OR REPLACE FUNCTION" does not clear search_path
Date
Msg-id 15993-a0c0026150beb40a@postgresql.org
Whole thread Raw
Responses Re: BUG #15993: "CREATE OR REPLACE FUNCTION" does not clearsearch_path
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      15993
Logged by:          Alexander Pavlov
Email address:      alexander.pavlov.rus@gmail.com
PostgreSQL version: 10.9
Operating system:   Debian
Description:

-- this will correctly create function with empty search_path
CREATE OR REPLACE FUNCTION MY_FUNC () RETURNS BOOLEAN AS $$ BEGIN RETURN
TRUE;END;$$ LANGUAGE PLPGSQL;

-- this will correctly update function to have "PUBLIC, MY_SCHEMA" search
path
CREATE OR REPLACE FUNCTION MY_FUNC () RETURNS BOOLEAN AS $$ BEGIN RETURN
TRUE;END;$$ LANGUAGE PLPGSQL SET SEARCH_PATH TO PUBLIC, MY_SCHEMA;

-- this will correctly update function to have "MY_SCHEMA" search path
CREATE OR REPLACE FUNCTION MY_FUNC () RETURNS BOOLEAN AS $$ BEGIN RETURN
TRUE;END;$$ LANGUAGE PLPGSQL SET SEARCH_PATH TO MY_SCHEMA;

-- this will NOT update function to have empty search path, search path will
remain "MY_SCHEMA", as at previous "create or replace" call
CREATE OR REPLACE FUNCTION MY_FUNC () RETURNS BOOLEAN AS $$ BEGIN RETURN
TRUE;END;$$ LANGUAGE PLPGSQL;


pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: ERROR: multixact X from before cutoff Y found to be still running
Next
From: PG Bug reporting form
Date:
Subject: BUG #15994: can't run psql