My application does not use any transactions (other than the implicit per statement ones that must exist), but I think I did edit some functions in pgadmin around that time so it may be that bug or something similar/related.
I didn't bother to upgrade to 8.1.4 because I thought it was just a security fix that didn't apply to me. I'll upgrade tonight during off hours. ----- Original Message ----- From: "Tom Lane" <[EMAIL PROTECTED]> To: "Cstdenis" <[EMAIL PROTECTED]> Cc: <pgsql-bugs@postgresql.org> Sent: Friday, May 26, 2006 8:05 PM Subject: Re: [BUGS] BUG #2458: Postgresql crash > "Cstdenis" <[EMAIL PROTECTED]> writes: > > [ SIGSEGV in plpgsql_xact_cb ] > > I think this is probably an instance of the bug patched here: > http://archives.postgresql.org/pgsql-committers/2006-03/msg00022.php > > If you're certain that your applications never redefine a plpgsql > function that might be in active use, then we might need to look > harder. Otherwise, please update to 8.1.4 and see if the problem > recurs ... > > regards, tom lane > ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
