Re: lock entire database

Oliver Fromme wrote:

>Benjamin wrote:
> > Machine A is the Primary, and Machine B is the backup for A.
> > When B is booting up, it has to duplicate the entire pgsql db from A.
> > As Ron said, cud do with a pg_dump. But, i guess, pg_dump takes quite
> > some time. As A is already up, it wud be unwise to lock the db for so
> > long. Also, even if i do go ahead with pg_dump, and then do a pg_restore
> > on B, by the time data is being pg_restore'ed on B, a query cud modify/
> > update the db on A.
> > My idea was to lock the db on A, scp the required files onto B and then
> > unlock db on A.
>
>If I understand you correctly, "Slony" will do exactly what you
>want, without the need to lock any DB: http://www.slony.org
>Slony 1.0 has been released recently, which was mentioned
>prominently on PostgreSQL's homepage. It's a master-slave
>replication system.
>
>Hope that helps.
>
>Best regards
> Oliver
>
Thanx everyone.
Yea.. slony seems to be good. We just might HAVE to use that in the near
future.
But as of now, we r shutting down pgsql on A, while the duplication is
being done, as Tom suggested.

--

Benjamin Jacob.

Disclaimer :
------------------------------------------------------------------------------
If you are not the intended recipient of this transmission to whom it is
addressed, or have received this transmission in error, you are hereby
notified that any dissemination, distribution or copying of this transmission
is strictly prohibited. Please notify us immediately and delete this e-mail
from your system. The sender does not accept liability for any errors or
omissions in the contents of this message which arise as a result of e-mail
transmission, which cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, arrive at wrong address or contain viruses. If verification
is required please request a hard-copy version. This e-mail contains only the
personal opinions of the sender and does not represent an official
communication from NetYantra of any manner.
------------------------------------------------------------------------------