Re: Replication
От | Jonathan Tripathy |
---|---|
Тема | Re: Replication |
Дата | |
Msg-id | 4CCFB6CF.4060006@abpni.co.uk обсуждение исходный текст |
Ответ на | Re: Replication (Scott Marlowe <scott.marlowe@gmail.com>) |
Ответы |
Re: Replication
Re: Replication Re: Replication |
Список | pgsql-general |
On 02/11/10 01:56, Scott Marlowe wrote: > On Mon, Nov 1, 2010 at 4:39 PM, Jonathan Tripathy<jonnyt@abpni.co.uk> wrote: >> On 01/11/10 21:10, Vick Khera wrote: >>> On Mon, Nov 1, 2010 at 3:53 PM, Jonathan Tripathy<jonnyt@abpni.co.uk> >>> wrote: >>>> The standby must support INSERTS and UPDATES as well (once the master has >>>> failed) >>>> >>>> Are there any solutions like this? Looking on the Postgresql site, all >>>> the >>>> standby solutions seem to be read only.. >>> If they are RO it is only while they are replicas, not masters. Once >>> the server is upgraded to the master role, it becomes RW. >>> >> So in the "Hot Standby" setup as described in >> http://www.postgresql.org/docs/current/static/hot-standby.html , how would I >> automatically make the slave a master? > I think you're looking for this: > http://www.postgresql.org/docs/current/static/warm-standby-failover.html > What is the difference between the "Hot-Standby" and "Warm-Standby"? Is the only different that the "Hot-Standby" standby servers are read-only, whereas the "Warm-Standby" standbys can't be queried at all? Thanks
В списке pgsql-general по дате отправления: