Re: lock entire database
| От | Scott Marlowe |
|---|---|
| Тема | Re: lock entire database |
| Дата | |
| Msg-id | 1092041456.27166.300.camel@localhost.localdomain обсуждение исходный текст |
| Ответ на | lock entire database (Benjamin <benjamin@netyantra.com>) |
| Список | pgsql-novice |
On Sun, 2004-08-08 at 23:35, Benjamin wrote: > Scott Marlowe wrote: > Ok. The scene now. > 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. > > Is the picture clear now? > In addition to my previous post, or wait until 8.0 and use pitr to do this.
В списке pgsql-novice по дате отправления: