On Wed, 22 Jan 2020 at 23:22, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Thomas Kellerer <shammat@gmx.net> writes:
> > Tom Lane schrieb am 22.01.2020 um 16:05:
> >> Right. It's the XA transaction manager's job not to forget uncommitted
> >> transactions. Reasoning as though no TM exists is not only not very
> >> relevant, but it might lead you to put in features that actually
> >> make the TM's job harder. In particular, a timeout (or any other
> >> mechanism that leads PG to abort or commit a prepared transaction
> >> of its own accord) does that.
>
> > That's a fair point, but the reality is that not all XA transaction managers
> > do a good job with that.
>
> If you've got a crappy XA manager, you should get a better one, not
> ask us to put in features that make PG unsafe to use with well-designed
> XA managers.
Agreed. Or use some bespoke script that does the cleanup that you
think is appropriate for your particular environment and set of bugs.
--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise