From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | pawel(dot)ziewiecki(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works |
Date: | 2023-10-18 20:16:06 |
Message-ID: | 30b6cf10e35816cb375cdf7b5266727d862b0361.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, 2023-10-18 at 17:01 +0000, PG Bug reporting form wrote:
> Operating system: aws rds postgresql
>
> postgres=> create database u1db with owner u1;
> CREATE DATABASE
> postgres=> \c u1db
> psql (15.4 (Debian 15.4-1.pgdg120+1), server 15.3)
> You are now connected to database "u1db" as user "u1".
> u1db=> create table public.t1 (id int);
> ERROR: permission denied for schema public
> LINE 1: create table public.t1 (id int);
> ^
> u1db=> alter table public.t1 owner to u1;
> ERROR: relation "public.t1" does not exist
> u1db=> create table public.t1 (id int);
> CREATE TABLE
> u1db=> \d
> List of relations
> Schema | Name | Type | Owner
> --------+------+-------+-------
> public | t1 | table | u1
> (1 row)
I cannot reproduce that on real PostgreSQL.
Perhaps you should ask Amazon if they modified the permission system somehow.
If that's a bug, I'd say it is not a PostgreSQL bug.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-10-18 20:17:58 | Re: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works |
Previous Message | Laurenz Albe | 2023-10-18 20:15:58 | Re: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works |