| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov> |
| Subject: | Re: [PATCH] V3: Idle in transaction cancellation |
| Date: | 2010-12-16 21:30:02 |
| Message-ID: | 1292534933-sup-1927@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tom Lane's message of jue dic 16 17:54:51 -0300 2010:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Thu, Dec 16, 2010 at 3:41 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gevik Babakhani | 2010-12-16 21:31:58 | clang and LLVM |
| Previous Message | Tom Lane | 2010-12-16 20:54:51 | Re: [PATCH] V3: Idle in transaction cancellation |