SET search_path = value

From: Erwin Brandstetter <brandstetter(at)falter(dot)at>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: SET search_path = value
Date: 2010-04-19 02:43:54
Message-ID: 4BCBC36A.9000706@falter.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi developers!

Just created a ticket concerning a minor error in the reverse engineered
SQL code for roles

Besides the example ...
ALTER ROLE SET search_path = test, public;
--> ALTER DATABASE test SET search_path='test, public'; -- quotes are
wrong
... there are at least two more occurrances:
ALTER FUNCTION ...
ALTER DATABASE ...

_If_ you wanted to quote the schema names, it would have to be quotes
around _each_ schema in the list, like so:
ALTER DATABASE test SET search_path = 'test', 'public';
But that would lead to another pitfall. This does not work as intended:
ALTER DATABASE test SET search_path = '"$user", public';
So, best not to add single quotes at all:
ALTER DATABASE test SET search_path ="$user", public;

The official docs on the matter are also misleading, IMO.
http://www.postgresql.org/docs/8.4/interactive/runtime-config-client.html
I've sent a comment on the website.

Regards
Erwin

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2010-04-19 11:03:02 Re: Ticket 3: groups of servers
Previous Message pgAdmin Trac 2010-04-19 01:57:56 Re: [pgAdmin III] #169: SET search_path = value