Диссертация (1149623), страница 21
Текст из файла (страница 21)
(These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the sequence. However, asuperuser can alter ownership of anysequence anyway.)3To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the type'sschema. (These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the type. However, asuperuser can alter ownership of anytype anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the type'sschema.
(These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the type. However, asuperuser can alter ownership of anytype anyway.)4To alter the owner, you must also bea direct or indirect member of thenew owning role, and that role musthave CREATE privilege on thetable's schema. (These restrictions enforce that altering the owner doesn'tdo anything you couldn't do by dropping and recreating the table. However, a superuser can alter ownershipof any table anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the table'sschema.
(These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the table. However, asuperuser can alter ownership of anytable anyway.)5alter the owner, you must also be a direct or indirect member of the newowning role, and that role must haveCREATE privilege on the conversion's schema. (These restrictions enforce that altering the owner doesn't doanything you couldn't do by droppingand recreating the conversion. However, a superuser can alter ownershipof any conversion anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the conversion'sschema.
(These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the conversion. However, asuperuser can alter ownership of anyconversion anyway.)120№ НайденоTo alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the view'sschema. (These restrictions enforce6 that altering the owner doesn't do anything you couldn't do by dropping andrecreating the view. However, asuperuser can alter ownership of anyview anyway.)ОтредактированоTo alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the view'sschema. (These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the view.
However, asuperuser can alter ownership of anyview anyway.)7To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the operator'sschema. (These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the operator. However, asuperuser can alter ownership of anyoperator anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the operator'sschema.
(These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the operator. However, asuperuser can alter ownership of anyoperator anyway.)8alter the owner, you must also be a direct or indirect member of the newowning role, and that role must haveCREATE privilege on the materialized view's schema. (These restrictions enforce that altering theowner doesn't do anything you couldn't do by dropping and recreating thematerialized view. However, asuperuser can alter ownership of anyview anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the materializedview's schema. (These restrictions enforce that altering the owner doesn't doanything you couldn't do by droppingand recreating the materialized view.However, a superuser can alter ownership of any view anyway.)9To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the operatorclass's schema.
(These restrictions enforce that altering the owner doesn't doanything you couldn't do by droppingand recreating the operator class.However, a superuser can alter ownership of anyTo alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the operatorclass's schema. (These restrictions enforce that altering the owner doesn't doanything you couldn't do by droppingand recreating the operator class. However, a superuser can alter ownershipof any operator class anyway.)121№ НайденоTo alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the collation'sschema.
(These restrictions enforce10 that altering the owner doesn't do anything you couldn't do by dropping andrecreating the collation. However, asuperuser can alter ownership of anycollation anyway.)ОтредактированоTo alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the collation'sschema. (These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the collation. However, asuperuser can alter ownership of anycollation anyway.)alter the owner, you must also be a direct or indirect member of the newowning role, and that role must haveCREATE privilege on the aggregatefunction's schema.
(These restrictions11 enforce that altering the owner doesn'tdo anything you couldn't do by dropping and recreating the aggregatefunction. However, a superuser can alter ownership of anyTo alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the aggregatefunction's schema. (These restrictionsenforce that altering the owner doesn'tdo anything you couldn't do by dropping and recreating the aggregate function. However, a superuser can alterownership of any aggregate functionanyway.)alter the owner, you must also be a direct or indirect member of the newowning role, and that role must haveCREATE privilege on the function'sschema.
(These restrictions enforce12 that altering the owner doesn't do anything you couldn't do by dropping andrecreating the function. However, asuperuser can alter ownership of anyfunction anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the function'sschema.
(These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the function. However, asuperuser can alter ownership of anyfunction anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the domain'sschema.
(These restrictions enforce13 that altering the owner doesn't do anything you couldn't do by dropping andrecreating the domain. However, asuperuser can alter ownership of anydomain anyway.)To alter the owner, you must also be adirect or indirect member of the newowning role, and that role must haveCREATE privilege on the domain'sschema. (These restrictions enforcethat altering the owner doesn't do anything you couldn't do by dropping andrecreating the domain. However, asuperuser can alter ownership of anydomain anyway.)122.















