> I don't think there is any way to handle cases where the master or slave
> just disappears. The other machine isn't under the server's control, so
> it has no way of it knowing. I think we have to allow the administrator
> to set a timeout, or ask to wait indefinately, and allow them to call an
> external program to record the event or notify administrators.
> Multi-master replication has the same issues.
Needs to wait indefinitely, a timeout is not acceptable since it leads to
inconsistent data. Human (or monitoring software) intervention is needed
if they can't reach each other in a reasonable time.
I think this needs to be kept dumb. Different sorts of use cases will simply
need different answers to resolve in-doubt transactions. What is needed is an
interface that allows listing and commit/rollback of in-doubt transactions
(preferably from a newly started client, or a direct command for the postmaster).
pgsql-hackers by date
|Next:||From: Zeugswetter Andreas SB SD||Date: 2003-09-29 14:41:11|
|Subject: Re: 2-phase commit|
|Previous:||From: Tom Lane||Date: 2003-09-29 14:30:40|
|Subject: Re: pgsql-server/src/backend catalog/index.c comma ... |