[
https://issues.apache.org/jira/browse/HAWQ-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270256#comment-16270256
]
Kuien Liu commented on HAWQ-1556:
---------------------------------
A coarse way to bypass it is to use REASSIGN:
REASSIGN OWNED BY old_role [, ...] TO new_role
It is strange that both ALTER OWNER and REASSIGN OWNED are invoking the same
underlaying functions, but alter.c disabled them while user.c clears.
> Support more statements with ALTER OWNER
> ----------------------------------------
>
> Key: HAWQ-1556
> URL: https://issues.apache.org/jira/browse/HAWQ-1556
> Project: Apache HAWQ
> Issue Type: New Feature
> Components: DDL
> Reporter: Kuien Liu
> Assignee: Radar Lei
>
> Except _AlterAggregateOwner_ and _AlterFunctionOwner_, _ExecAlterOwnerStmt_
> has commented out all the other statements (comparing with GPDB branch).
> ```
> # create type complex as (x integer, y integer);
> # create role kuien;
> # alter type complex owner to kuien;
> ERROR: Cannot support alter type owner statement yet
> ```
> It is not too user friendly, AND I see no reason why not support them. What
> do you think? Any plan on this?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
