set search_path command

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 Countrieswww.replicon.com
<http://www.replicon.com/> | facebook
<http://www.facebook.com/Replicon.inc> | twitter
<http://twitter.com/Replicon> | blog
<http://www.replicon.com/blog/> | contact us
<http://www.replicon.com/about_replicon/contact_us.aspx> We are
hiring! | search jobs
<http://tbe.taleo.net/NA2/ats/careers/searchResults.jsp?org=REPLICON&cws=1&act=sort&sortColumn=1&__utma=1.651918544.1299001662.1299170819.1299174966.10&__utmb=1.8.10.1299174966&__utmc=1&__utmx=-&__utmz=1.1299174985.10.3.utmcsr=google%7Cutmccn=(organic)%7Cutmcmd=organic%7Cutmctr=replicon%20careers&__utmv=1.%7C3=Visitor%20Type=Prospects=1,&__utmk=40578466>
*