Skip to main content

Replication and Object Ownership

  • October 17, 2017
  • 1 reply
  • 5 views

Jim_Knicely
Forum|alt.badge.img+2

Hi,

I have a client that is replicating a schema from one Vertica cluster to another. If a replicated object does not exist on the remote cluster, Vertica will create it. However, the owner of the created object is dbadmin (or whatever the client is using as the admin user), not the original owner.

Is this by design? Are we expecting the client to change the ownership of the object after replication?

Thanks!

1 reply

Jim_Knicely
Forum|alt.badge.img+2
  • Author
  • Participating Frequently
  • October 20, 2017

Fyi ... The documentation does report this about "Ownership of Restored Objects":

"When performing a restore, Vertica inserts data into existing database objects. By default, the restore does not affect the ownership, storage policies, or permissions of the restored objects. If, however, the restored object does not currently exist, Vertica re-creates it. In this situation, the restored object is owned by the user (DBADMIN) performing the restore. Vertica does not restore dependent grants, roles, or client authentications with restored objects."

See:
https://my.vertica.com/docs/9.0.x/HTML/index.htm#Authoring/AdministratorsGuide/BackupRestore/OwnershipofRestoredObjects.htm

Replication must also follow that restore logic.

Dave Thompson: Thanks for pointing this out!