| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
| Cc: | 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 18:18:36 |
| Message-ID: | C4DB0B54-B5DF-4E58-BB09-26717E8F7AE2@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Jul 5, 2022, at 11:12, Bryn Llewellyn <bryn(at)yugabyte(dot)com> wrote:
> Finally, what do you think of a possible future enhancement to allow setting a null search_path?
You use the empty string, rather than NULL, but it works right now:
xof=# show search_path;
search_path
-----------------
"$user", public
(1 row)
xof=# select * from t;
i | d1 | d2
---+----+----
(0 rows)
xof=# set search_path='';
SET
xof=# show search_path;
search_path
-------------
""
(1 row)
xof=# select * from t;
ERROR: relation "t" does not exist
LINE 1: select * from t;
^
xof=#
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2022-07-05 18:24:17 | Re: Seems to be impossible to set a NULL search_path |
| Previous Message | Adrian Klaver | 2022-07-05 18:18:29 | Re: Seems to be impossible to set a NULL search_path |