On Thu, 2010-10-07 at 19:44 -0400, Greg Smith wrote: > I don't see this as needing any implementation any more complicated than > the usual way such timeouts are handled. Note how long you've been > trying to reach the standby. Default to -1 for forever. And if you hit > the timeout, mark the standby as degraded and force them to do a proper > resync when they disconnect. Once that's done, then they can re-enter > sync rep mode again, via the same process a new node would have done so.
What I don't understand is why this isn't obvious to everyone. Greg this is very well put and the -hackers need to start thinking like people that actually use the database. JD -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
