On Fri, 2006-11-03 at 01:48 -0500, Tom Lane wrote:
I agree that there's a usability issue here though; I've been burnt by
forgotten prepared xacts myself (eg by control-C'ing pg_regress at just
the wrong time). Would it help if we included prepared xacts in the
pg_stat_activity view?
Is
Simon Riggs [EMAIL PROTECTED] writes:
We only care when they break, otherwise its just situation normal, yes?
No, the trouble case is where the XA manager that owns the transaction
has forgotten about it.
Is there a way to see prepared transactions where the original session
that prepared
On Fri, 3 Nov 2006, Tom Lane wrote:
Is there a way to see prepared transactions where the original session
that prepared then has died? Perhaps the message at startup should be
you have at least one prepared transaction that needs resolution.
I am completely baffled by this focus on
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
We only care when they break, otherwise its just situation normal, yes?
No, the trouble case is where the XA manager that owns the transaction
has forgotten about it.
Yeah, and there's no way the DBMS can detect that.
Is there a way to
