Re: AtAbort_Portsl problem

Tatsuo Ishii <ishii@postgresql.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