Re: Duplicating a database

From: Karim Nassar <Karim(dot)Nassar(at)NAU(dot)EDU>
To: Scott Marlowe <smarlowe(at)qwest(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Duplicating a database
Date: 2004-10-24 04:22:20
Message-ID: 1098591740.9599.245.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2004-10-24 04:39:36 Re: Linking question
Previous Message Bruno Wolff III 2004-10-24 04:15:57 Re: '1 year' = '360 days' ????