Re: Parameter name standby_mode
От | Joachim Wieland |
---|---|
Тема | Re: Parameter name standby_mode |
Дата | |
Msg-id | dc7b844e1002101010x78f83f34w54ddddc524bd1589@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parameter name standby_mode (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Список | pgsql-hackers |
On Wed, Feb 10, 2010 at 12:16 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > If they want to implement the warm standby using the (new) built-in > logic to keep retrying restore_command, they would set > standby_mode='on'. standby_mode='on' doesn't imply streaming replication. > > If you want to use pg_standby or similar tools, then you would indeed > set standby_mode='off', but I think that makes sense because you're > implementing the standby functionality outside the server in that case. Okay, got it now with your explanations. For some reason it didn't work before with standby_mode = 'on' (it does now) and the warning "FATAL: sorry, too many standbys already" gave me a first suspicion that SR is the only use case for this. Then I checked the docs and there it said "If this parameter is on, the streaming replication is enabled". I understand now what it does and that it is a prerequisite but that there is also a non-SR use case... So the name is okay for me :-) Thanks again, Joachim
В списке pgsql-hackers по дате отправления: