| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | kalimira(dot)boris(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16195: current_schema always return "public" |
| Date: | 2020-01-07 16:29:42 |
| Message-ID: | CAOBaU_Y9X1mjWE0E5jBpqgjbJKS=Okm-D8=yPyR_f_LuqcTBbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jan 7, 2020 at 5:07 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 16195
> Logged by: Boris Kalimira
> Email address: kalimira(dot)boris(at)gmail(dot)com
> PostgreSQL version: 12.1
> Operating system: CentOS 7 & Windows
> Description:
>
> 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
Is "test" role owner of the "test" schema, or does it have usage
privilege on it?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-07 18:06:08 | 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 |
| Previous Message | PG Bug reporting form | 2020-01-07 16:06:05 | BUG #16195: current_schema always return "public" |