Re: set search_path failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: chriskl(at)familyhealth(dot)com(dot)au, pgsql-hackers(at)postgresql(dot)org
Subject: Re: set search_path failure
Date: 2002-08-19 13:53:50
Message-ID: 6397.1029765230@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> The man page says:
> SET variable { TO | = } { value | 'value' | DEFAULT }

> So user naturally thinks
> set search_path to 'public,s1';
> is a correct syntax, no?

The man page needs improvement --- some variables accept a list of
values now. In particular
SET search_path = public, s1;
SET search_path = "public", "s1";
SET search_path = 'public', 's1';
would all be correct ways of expressing this. The other is not, and
can't be because it would require excluding commas from the set of
characters allowed in quoted schema names.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Curt Sampson 2002-08-19 13:56:04 Re: Inheritance
Previous Message Tom Lane 2002-08-19 13:46:50 Re: Function result cacheing - any comments?