Re: time-delayed standbys
От | Jaime Casanova |
---|---|
Тема | Re: time-delayed standbys |
Дата | |
Msg-id | BANLkTi=OuMtTXwj9j9iVasb6Ee+EnSHaVQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: time-delayed standbys (Fujii Masao <masao.fujii@gmail.com>) |
Список | pgsql-hackers |
On Wed, Jun 15, 2011 at 12:58 AM, Fujii Masao <masao.fujii@gmail.com> wrote: > > http://forge.mysql.com/worklog/task.php?id=344 > According to the above page, one purpose of time-delayed replication is to > protect against user mistakes on master. But, when an user notices his wrong > operation on master, what should he do next? The WAL records of his wrong > operation might have already arrived at the standby, so neither "promote" nor > "restart" doesn't cancel that wrong operation. Instead, probably he should > shutdown the standby, investigate the timestamp of XID of the operation > he'd like to cancel, set recovery_target_time and restart the standby. > Something like this procedures should be documented? Or, we should > implement new "promote" mode which finishes a recovery as soon as > "promote" is requested (i.e., not replay all the available WAL records)? > i would prefer something like "pg_ctl promote -m immediate" that terminates the recovery -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación
В списке pgsql-hackers по дате отправления: