Re: Set new owner on cloned database

From: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
To: pgsql-general(at)postgresql(dot)org
Cc: byrnejb(at)harte-lyne(dot)ca
Subject: Re: Set new owner on cloned database
Date: 2010-12-08 21:41:18
Message-ID: 20101208224118.2924e519@dawn.webthatworks.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 8 Dec 2010 13:40:29 -0500 (EST)
"James B. Byrne" <byrnejb(at)harte-lyne(dot)ca> wrote:

> I am testing a Rails deployment and wish to copy a database
> assigning it an new owner. I have tried this:
>
> createdb --owner=hll_theheart_db_devl
> --template=hll_th_deploytest_prod hll_theheart_devl
>
> While this indeed sets the database owner to hll_theheart_db_devl
> everything else, schema, tables whatever, remains owned by the
> original owner. Is there no way to change the owner everywhere in
> the cloned database using cretedb? Or am I constrained to do a
> dump all and restore?

http://www.mail-archive.com/pgsql-hackers(at)postgresql(dot)org/msg51048.html
http://www.mail-archive.com/pgsql-hackers(at)postgresql(dot)org/msg51047.html

I'm not sure if there has been any progress in newer postgres to
support easier change of owner.
I'm not aware of any more current better solution.

Unfortunately I think the license of the above didn't help to make
people willing to improve and make the code more popular.

--
Ivan Sergio Borgonovo
http://www.webthatworks.it

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Reuven M. Lerner 2010-12-08 22:32:00 Re: Hanging with pg_restore and large objects
Previous Message Simon Riggs 2010-12-08 20:55:33 Re: pg_standby logging issues