Re: Cancelling idle in transaction state

From: Kris Jurka <books(at)ejurka(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Joachim Wieland <joe(at)mcknight(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, James Pye <lists(at)jwp(dot)name>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cancelling idle in transaction state
Date: 2009-12-30 12:28:01
Message-ID: alpine.BSO.2.00.0912300726540.19439@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 30 Dec 2009, Heikki Linnakangas wrote:

> Could we send an asynchronous notification immediately when the
> transaction is cancelled, but also change the error message you get in
> the subsequent commands. Clients that ignore the async notification
> would still see a proper error message at the ERROR.
>

+1

Kris Jurka

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2009-12-30 12:30:23 Re: Cancelling idle in transaction state
Previous Message Magnus Hagander 2009-12-30 12:26:44 Re: msvc build fails in Japanese environment