From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: backup database by cloning itself |
Date: | 2007-02-15 20:25:13 |
Message-ID: | 45D4C1A9.4020906@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/14/07 01:14, filippo wrote:
> On 13 Feb, 14:54, "filippo" <filippo2(dot)(dot)(dot)(at)virgilio(dot)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-----
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Elgert | 2007-02-15 20:37:51 | Re: Database performance comparison paper. |
Previous Message | Bill Moran | 2007-02-15 20:06:57 | Re: Database performance comparison paper. |