Bug introduced by recent ALTER OWNER permissions check change - Mailing list pgsql-hackers

From Tom Lane
Subject Bug introduced by recent ALTER OWNER permissions check change
Date
Msg-id 10504.1123118119@sss.pgh.pa.us
Whole thread Raw
Responses Re: Bug introduced by recent ALTER OWNER permissions check change  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
postgres=# create user u1;
CREATE ROLE
postgres=# create schema s1;
CREATE SCHEMA
postgres=# create table s1.t1(f1 int);
CREATE TABLE
postgres=# alter table s1.t1 owner to u1;
ERROR:  permission denied for schema s1
postgres=#

Considering I am superuser, it should darn well allow this.

The problem of course is the test that u1 would have the rights to
create t1 in s1, which he doesn't.  I think we have to skip that
test if superuser.  As long as we need an explicit test on
superuserness, we may as well skip *all* the added code.

Comments?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Solving the OID-collision problem
Next
From: "Qingqing Zhou"
Date:
Subject: Re: Fundamental error in "no WAL log" index/file creation stuff