Re: [PATCH] V3: Idle in transaction cancellation

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Greg Smith <greg@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>, Kevin Grittner <kevin.grittner@wicourts.gov>
Date: 2010-12-16T21:30:02Z
Lists: pgsql-hackers
Excerpts from Tom Lane's message of jue dic 16 17:54:51 -0300 2010:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Thu, Dec 16, 2010 at 3:41 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> (But this is all speculation; I don't actually know SSL innards.)
> 
> > I would be really surprised if aborting a transaction takes long
> > enough to mess up SSL.  I mean, there could be a network delay at any
> > time, too.
> 
> Yeah, that's what I think too.  I was just wondering if there could be
> any situation where xact abort takes minutes.

Maybe if it's transaction commit there could be a long queue of pending
deferred triggers, but on abort, those things are discarded.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support