On Thu, Dec 9, 2010 at 11:54 PM, Fujii Masao wrote:
> In previous discussion, some people wanted the "wait-forever" option which
> blocks all the transactions on the master until sync'd standby has appeared,
> in order to reduce the risk of data loss in synchronous replication.
>
> What I'm not cl
3. Shutdown should abort all the blocking transactions?
* Problem is that a client thinks that those transactions have been
aborted
even though those WAL records have been written on the master. But
this is very common problem for DBMS, so we don't need to worry about
Hi,
In previous discussion, some people wanted the "wait-forever" option which
blocks all the transactions on the master until sync'd standby has appeared,
in order to reduce the risk of data loss in synchronous replication.
What I'm not clear is; How does smart or fast shudown advance while all
