| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Seems to be impossible to set a NULL search_path |
| Date: | 2022-07-05 23:33:43 |
| Message-ID: | eded5913-b6dc-9957-c4b1-a3009a03f953@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-07-06 00:49:57 | Re: General Inquiry |
| Previous Message | Bryn Llewellyn | 2022-07-05 22:08:27 | Re: Seems to be impossible to set a NULL search_path |