Re: recovery_connections cannot start (was Re: master in standby mode croaks)
От | Robert Haas |
---|---|
Тема | Re: recovery_connections cannot start (was Re: master in standby mode croaks) |
Дата | |
Msg-id | m2q603c8f071004231429jc7a41dcah4aeb727172db328f@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: recovery_connections cannot start (was Re: master in standby mode croaks) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: recovery_connections cannot start (was Re: master in
standby mode croaks)
|
Список | pgsql-hackers |
On Fri, Apr 23, 2010 at 4:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Simon Riggs <simon@2ndQuadrant.com> writes: >> How about something like > >> wal_additional_info = none | archive | connect > > "connect" seems like a completely inappropriate word here. It is > not obviously related to HS slaves and it could be taken to refer > to ordinary database connections (sessions). > > Personally I agree with your objection to "crash" but not with the > objection to "standby". Maybe this would be appropriate: > > wal_mode = minimal | archive | hot_standby I was thinking maybe "log_shipping" instead of "archive", since we're conflating the technology (log shipping) with the technology used to implement it (archiving or streaming). Possible "crash_recovery" rather than just "crash" where you have "mimimal". I don't love "hot_standby" either but it might be the least of evils. ...Robert
В списке pgsql-hackers по дате отправления: