Re: AtAbort_Portsl problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: AtAbort_Portsl problem
Date: 2010-01-18 00:41:29
Message-ID: 15501.1263775289@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> While ago, I reported a problem regarding exec_execute_message crash
> in transaction abort state if sync message issued right after parse,
> bind and execute message (which is normal if used with pgpool). After
> further investigation, I concluded that there's a serious problem with
> unnamed portal handling.

I was never able to get your test case to work (or, rather, crash).
Does this patch address the original issue, or is this something
different?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2010-01-18 00:49:46 Re: AtAbort_Portsl problem
Previous Message Tatsuo Ishii 2010-01-18 00:35:16 AtAbort_Portsl problem