Peter Eisentraut <peter_e@gmx.net> writes:
> In any case, if either the existing session of the TM is cut or it
> cannot create a new connection, it will, after some time, have to give
> up roll back the prepared transactions on the other servers. So some
> kind of setting to not shut down if there are prepared transactions
> pending could be useful. But this could probably be a separate GUC
> setting or two instead of a shutdown mode (or two) of its own.
This argument still seems pretty bogus. The *entire* point of a TM
is to cope with crashes of individual databases under its management.
The proposed setting seems to amount to a "please don't crash" GUC,
which is silly on its face, and does not actually make the TM's life
any easier anyway.
regards, tom lane
