Re: Seems to be impossible to set a NULL search_path
| От | Adrian Klaver |
|---|---|
| Тема | Re: Seems to be impossible to set a NULL search_path |
| Дата | |
| Msg-id | eded5913-b6dc-9957-c4b1-a3009a03f953@aklaver.com обсуждение исходный текст |
| Ответ на | Re: Seems to be impossible to set a NULL search_path (Bryn Llewellyn <bryn@yugabyte.com>) |
| Список | 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 по дате отправления: