Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WraFl-0007BV-MU for pgsql-admin@arkaria.postgresql.org; Mon, 02 Jun 2014 21:58:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WraFl-0002nZ-5P for pgsql-admin@arkaria.postgresql.org; Mon, 02 Jun 2014 21:58:49 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WraFj-0002nL-Vp for pgsql-admin@postgresql.org; Mon, 02 Jun 2014 21:58:48 +0000 Received: from mail-qa0-x22f.google.com ([2607:f8b0:400d:c00::22f]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1WraFg-0001cP-NC for pgsql-admin@postgresql.org; Mon, 02 Jun 2014 21:58:45 +0000 Received: by mail-qa0-f47.google.com with SMTP id s7so3628916qap.20 for ; Mon, 02 Jun 2014 14:58:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type:content-transfer-encoding :content-disposition; bh=pfr3U3I0MlnHlPisIrjPP76bxQ/9+poRZnLehMadzoA=; b=lkpYP8G3j+dko6JpeJGFC/eNerZMWXeOJOyIkPsjBvpqtjVYt9Ekpt25kWgVR95HcS BNIB2uQOjAHK/jMrL/H9vKiFbvcsSlY8SViHQ/3g5cV8k0Z6WUSNu1beWgVq3edPuMzi yjNYBrlrK/enLt8c6DeWEaNAscF3csVt8fGESa2VSMo6KaJplEoroHHi4U/0sTd0k1ET 7f6fx2nEOi3SvFRgmuJi+Qs9q1vUOyLBbsr3LKyNZxGvmVqPYbo8pDGNeLo+91YN80DD 3X3QGWjKM9GE6eGEZ5qOuQWc4N6b5lHWfhX+sWppkc6Vx5F4FMUc0GY9ExWhfLhI9Y/j YQVw== X-Received: by 10.224.50.136 with SMTP id z8mr13623452qaf.66.1401746323517; Mon, 02 Jun 2014 14:58:43 -0700 (PDT) Received: from [172.24.38.116] (70-91-216-177-BusName-NewEngland.hfc.comcastbusiness.net. [70.91.216.177]) by mx.google.com with ESMTPSA id o88sm9142462qge.19.2014.06.02.14.58.42 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 02 Jun 2014 14:58:43 -0700 (PDT) Date: Mon, 2 Jun 2014 17:58:42 -0400 From: Vibhor Kumar To: Radovan Jablonovsky Cc: pgsql-admin Message-ID: <57498BFA3C404D6699D939A7B6A1B602@gmail.com> In-Reply-To: References: Subject: Re: set search_path command X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Monday, June 2, 2014 at 5:50 PM, Radovan Jablonovsky wrote: > 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) I think so. It was fixed in 9.2. E.14.3.1.7. Server Settings Silently ignore nonexistent schemas specified in search_path (Tom Lane) : This makes it more convenient to use generic path settings, which might include some schemas that don't exist in all databases. Thanks & Regards, Vibhor Kumar Blogs:http://vibhork.blogspot.com http://vibhorkumar.wordpress.com -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin