set search_path command - Mailing list pgsql-admin

From Radovan Jablonovsky
Subject set search_path command
Date
Msg-id CAJYcdTuW815KJ6enWLxNY__ZD5HJOuThmDhJT4i4b541TFL8=Q@mail.gmail.com
Whole thread Raw
Responses Re: set search_path command  (Vibhor Kumar <vibhor.aim@gmail.com>)
Re: set search_path command  (David G Johnston <david.g.johnston@gmail.com>)
List pgsql-admin
Hello,

When we compared behaviour of "set search_path" between 9.1.9 and 9.3.4, there is difference. On 9.1.9 the command "set search_path to schema1,public" checks if the schema exists and if not it return error. Example:
set search_path to "schema123",public;
ERROR:  invalid value for parameter "search_path": "schema123, public"
DETAIL:  schema "schema123" does not exist

On 9.3.4 the same command silently ignore the schema does not exists. Example:
set search_path to "schema123",public;
SET
 select * from pg_namespace where nspname ilike '%schema123%';
 nspname | nspowner | nspacl
---------+----------+--------
(0 rows)

Is this new behaviour intentional? 

Sincerely,
--

Radovan Jablonovsky | SaaS DBA | Phone 1-403-262-6519 (ext. 256) | Fax 1-403-233-8046


Replicon | Hassle-Free Time & Expense Management Software - 7,300 Customers - 70 Countries
www.replicon.com | facebook | twitter | blog | contact us

We are hiring! | search jobs

pgsql-admin by date:

Previous
From: Jorge Torralba
Date:
Subject: Re: Replication Delay
Next
From: Vibhor Kumar
Date:
Subject: Re: set search_path command