From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | alexander(dot)pavlov(dot)rus(at)gmail(dot)com |
Subject: | BUG #15993: "CREATE OR REPLACE FUNCTION" does not clear search_path |
Date: | 2019-09-06 20:42:02 |
Message-ID: | 15993-a0c0026150beb40a@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15993
Logged by: Alexander Pavlov
Email address: alexander(dot)pavlov(dot)rus(at)gmail(dot)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;
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2019-09-06 22:39:17 | BUG #15994: can't run psql |
Previous Message | Thomas Munro | 2019-09-06 20:40:53 | Re: ERROR: multixact X from before cutoff Y found to be still running |