Re: 2PC-induced lockup

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Subject: Re: 2PC-induced lockup
Date: 2007-07-12 15:17:25
Message-ID: 200707121117.26171.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday 12 July 2007 04:19, Simon Riggs wrote:
> On Wed, 2007-07-11 at 18:09 -0400, Tom Lane wrote:
> > > There seems like a number of ways that unresolved prepared transactions
> > > can cause problems. We really need to have startup mention how many
> > > prepared transactions there are, so we have some chance of
> > > understanding and resolving potential problems.
> >
> > While I have no particular objection to such a log entry, I doubt it
> > will fix anything; how many people will really think to look in the
> > postmaster log?
>
> Even if it were just you and me. From my perspective, thats enough.

Well, Tom doesn't look at the log files, so I guess your idea is shot...

:-)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2007-07-12 15:24:17 Re: "tuple concurrently updated" during index deletion
Previous Message Gregory Stark 2007-07-12 15:06:32 Re: [GENERAL] Count(*) throws error