From: | "Cstdenis" <cstdenis(at)ctgameinfo(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2458: Postgresql crash |
Date: | 2006-05-27 03:26:06 |
Message-ID: | 000101c6817a$8456ebc0$6401a8c0@chris |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Cstdenis" <cstdenis(at)fanart-central(dot)net>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Sent: Friday, May 26, 2006 8:05 PM
Subject: Re: [BUGS] BUG #2458: Postgresql crash
> "Cstdenis" <cstdenis(at)fanart-central(dot)net> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Volkan YAZICI | 2006-05-27 08:03:45 | Strange random() Correlation |
Previous Message | Tom Lane | 2006-05-27 03:05:52 | Re: BUG #2458: Postgresql crash |