public inbox for [email protected]  

help / color / mirror / Atom feed

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

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 there any other place we could make them
> more visible during normal server operation?

We only care when they break, otherwise its just situation normal, yes?

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". We
need something at that point, otherwise a PITR recovery is fairly likely
to contain them and we need to know that.

Otherwise on a system using prepared transactions heavily you may not
spot the odd or two that have crashed and need resolution. Presumably
they will effect oldestxmin, so its fairly important to be able to
resolve them in a timely manner or at least know they are there.

Not that I am advising their use though....

-- 
  Simon Riggs             
  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]
  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