Re: backup database by cloning itself - Mailing list pgsql-general

From Ron Johnson
Subject Re: backup database by cloning itself
Date
Msg-id 45D4C1A9.4020906@cox.net
Whole thread Raw
In response to Re: backup database by cloning itself  ("filippo" <filippo2991@virgilio.it>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/14/07 01:14, filippo wrote:
> On 13 Feb, 14:54, "filippo" <filippo2...@virgilio.it> wrote:
>
>> My target is to have the backup operation not affecting the users, so
>> I want to be able to copy a database even if the database is used by
>> someone.
>
> I could use pg_dump/pg_restore. pg_dump doesn't have to have exclusive
> access to database to perform the operation. My only problem is that
> pg_dump create a backup on a file, the best to me whould be to have a
> perfect clone (users/ data etc) of original database ready to be used
> just after the cloning. Is it possible?

pg_dump | pg_restore.

But you still haven't told us why you need copies of the database
every 2 hours.  What is the "business need" you are trying to solve.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF1MGpS9HxQb37XmcRAlYvAJ92Hl9wI/7mb/zOh1xsZwRHR8uDvQCdFKE2
SIdsgnhecZKpEUMWYARLWWA=
=lqeo
-----END PGP SIGNATURE-----

pgsql-general by date:

Previous
From: Dave Page
Date:
Subject: Re: Stored Procedure examples
Next
From: Casey Duncan
Date:
Subject: Where art thou pg_clog?