On 21/01/2011 15:55, Bill Moran wrote:
On the "no" side, doing this kind of thing is always complex. We have a
slew of other, very specialized scripts that do things like convert a
production database to a development database by sanitizing sensitive
data, or automatically deploy new database o
In response to Ivan Voras :
> On 21/01/2011 14:39, Bill Moran wrote:
> > In response to Ivan Voras:
> >
> >> A fairly frequent operation I do is copying a database between servers,
> >> for which I use pg_dump. Since the database contains some extensions -
> >> most notably hstore and tsearch2, wh
On 21/01/2011 14:39, Bill Moran wrote:
In response to Ivan Voras:
A fairly frequent operation I do is copying a database between servers,
for which I use pg_dump. Since the database contains some extensions -
most notably hstore and tsearch2, which need superuser privileges to
install, I have a
In response to Ivan Voras :
> A fairly frequent operation I do is copying a database between servers,
> for which I use pg_dump. Since the database contains some extensions -
> most notably hstore and tsearch2, which need superuser privileges to
> install, I have a sort of a chicken-and-egg pro
A fairly frequent operation I do is copying a database between servers,
for which I use pg_dump. Since the database contains some extensions -
most notably hstore and tsearch2, which need superuser privileges to
install, I have a sort of a chicken-and-egg problem: the owner of the
database (and
