Re: max_standby_delay considered harmful
| От | Josh Berkus |
|---|---|
| Тема | Re: max_standby_delay considered harmful |
| Дата | |
| Msg-id | 4BE0AEEF.4070304@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: max_standby_delay considered harmful (Greg Smith <greg@2ndquadrant.com>) |
| Ответы |
Re: max_standby_delay considered harmful
Re: max_standby_delay considered harmful Re: max_standby_delay considered harmful Re: max_standby_delay considered harmful |
| Список | pgsql-hackers |
On 5/4/10 4:26 PM, Greg Smith wrote:
>
> Not the database's problem to worry about. Document that time should be
> carefully sync'd and move on. I'll add that.
Releasing a hot standby which *only* works for users with an operational
ntp implementation is highly unrealistic. Having built-in replication
in PostgreSQL was supposed to give the *majority* of users a *simple*
option for 2-server failover, not cater only to the high end. Every
administrative requirement we add to HS/SR eliminates another set of
potential users, as well as adding another set of potential failure
conditions which need to be monitored.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
В списке pgsql-hackers по дате отправления: