public inbox for [email protected]  

help / color / mirror / Atom feed

From: Heikki Linnakangas <[email protected]>
To: Tom Lane <[email protected]>
Cc: Simon Riggs <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: "recovering prepared transaction" after serverrestart message
Date: Fri, 03 Nov 2006 15:06:50 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <e3b306b71615a24e1be5e713ad3df048@>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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 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 database startup time.  That's
> not where the problem is.

Agreed. Though one way to have orphaned prepared transactions is to 
recover from a PITR backup or bring a warm stand-by live. The 
transaction manager might have committed a transaction after the backup 
was taken. Recovering from the backup resurrects the transaction again 
and the TM won't know about it.

The problem of orphaned transactions is most likely to occur on a 
dev/test environment, where the TM is run on a developer's laptop and 
might be killed and reinstalled or reconfigured at any time.

And unfortunately there's also a lot of broken TMs out there that don't 
recover from crashes properly.

I think it's a good idea to at least LOG about prepared transactions at 
startup. But it would be nice to also have a timeout, after which a big 
fat WARNING would be printed. I don't believe in killing transactions 
automatically though, that's a job for the administrator.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: "recovering prepared transaction" after serverrestart message
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox