Re: Duplicating a database - Mailing list pgsql-general

From Karim Nassar
Subject Re: Duplicating a database
Date
Msg-id 1098591740.9599.245.camel@localhost
Whole thread Raw
In response to Re: Duplicating a database  ("Scott Marlowe" <smarlowe@qwest.net>)
List pgsql-general
If you just need a working copy, not necessarily right up to date at any
> time, you can just dump and restore it:
>
> pg_dumpall -h source_server |psql -h dest_server
>
> add switches as necessary.

That would be great for the first time. But what I want to do is copy
~postgresql/data, stomping/deleting as necessary. Roughly, my thinking
is a daily cron job on the server:

  rm -rf /safe/dir/data
  /etc/init.d/postgresql stop
  tar czf - -C ~postgres data | tar xzf - -C /safe/dir/
  /etc/init.d/postgresql start


And a client script:

  /etc/init.d/postgresql stop
  rm -rf ~postgres/data
  ssh user@server tar czf - -C /safe/dir data|tar xvzf - -C ~postgres
  /etc/init.d/postgresql start

Or something similar with rsync instead of tar.

\<.

On Sat, 2004-10-23 at 18:04, Scott Marlowe wrote:
> On Thu, 2004-10-21 at 02:39, Karim Nassar wrote:
> > I need to have an exact copy of a postgres install on a testing
> > computer. I don't want to do slony. Is it feasible/reasonable to think
> > that I could just rsync to the devel boxen from the pg server? Or is
> > slony "The Way to Do It"(tm)?
>
> If you just need a working copy, not necessarily right up to date at any
> time, you can just dump and restore it:
>
> pg_dumpall -h source_server |psql -h dest_server
>
> add switches as necessary.


pgsql-general by date:

Previous
From: Karim Nassar
Date:
Subject: Re: Duplicating a database
Next
From:
Date:
Subject: Memory exhausted on DELETE.