Re: Seems to be impossible to set a NULL search_path - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Seems to be impossible to set a NULL search_path
Date
Msg-id eded5913-b6dc-9957-c4b1-a3009a03f953@aklaver.com
Whole thread Raw
In response to Re: Seems to be impossible to set a NULL search_path  (Bryn Llewellyn <bryn@yugabyte.com>)
List pgsql-general
On 7/5/22 15:08, Bryn Llewellyn wrote:

> I was informed by this precedent:
> 
> *truncate table u1.t1, t2;
> *
> It uses a comma-separated list of optionally qualified  SQL names.
> 
> And this:
> 
> «
> *CREATE SCHEMA schema_name ...
> *»

Those are creating objects. Set search_path is setting a configuration 
value.


> And then this:
> 
> «
> *SET [ SESSION | LOCAL ] configuration_parameter { TO | = } { value | 
> 'value' | DEFAULT }*
> 
> value — New value of parameter. Values can be specified as... 
> identifiers... or comma-separated lists of these, as appropriate for the 
> particular parameter...
> »
> 
> Notice that the token « value » in the syntax is not in quotes. I took 

Pretty sure it is:

{ TO | = } { value | 'value' | DEFAULT }





-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Bryn Llewellyn
Date:
Subject: Re: Seems to be impossible to set a NULL search_path
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: General Inquiry