| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | kalimira(dot)boris(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16195: current_schema always return "public" |
| Date: | 2020-01-09 04:15:21 |
| Message-ID: | 20200109041521.GH2251@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jan 07, 2020 at 04:06:05PM +0000, PG Bug reporting form wrote:
> Context:
> user "test" and schema "test" created on my DB.
>
> Connencted as test user on my DB:
> SHOW search_path -> "$user", public
> SELECT current_schema -> public
>
> Expectation -> SELECT current_schema -> test
With a database role named test:
=# show search_path ;
search_path
-----------------
"$user", public
(1 row)
=# select current_schema();
current_schema
----------------
public
(1 row)
=# create schema test;
CREATE SCHEMA
=# select current_schema();
current_schema
----------------
test
(1 row)
So your expectation is right, but not your test.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-01-09 04:38:09 | Re: libpq parameter parsing problem |
| Previous Message | Michael Paquier | 2020-01-09 04:06:12 | Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema |