Ryan Kelly <[email protected]> writes:
> It seems that ALTER TABLE ... OWNER TO does not change the ownership of
> any inheriting tables. The documentation states:
>> If ONLY is specified, only that table is altered. If ONLY is not
>> specified, the table and any descendant tables are altered.
If you read further (down in the Notes section of the ALTER TABLE page),
you'll find
The TRIGGER, CLUSTER, OWNER, and TABLESPACE actions never
recurse to descendant tables; that is, they always act as though
ONLY were specified.
So it is operating as intended and documented. If we were starting
from a green field I'd question whether these exceptions were a good
idea, but at this point changing the behavior seems more likely to break
user code than to help people. (In particular, the possible
consequences for reloading old dump files seem a bit scary, since
pg_dump emits lots of ALTER OWNER commands.)
regards, tom lane
--
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
