Tom Lane wrote:
Geoffrey <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, these make it clear that you've got some pretty big chunks of
nonstandard code in the backend, so my first thought is that there's a
memory-clobber bug somewhere in that.
I'm not sure what you mean by 'nonstandard code
Geoffrey <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Well, these make it clear that you've got some pretty big chunks of
>> nonstandard code in the backend, so my first thought is that there's a
>> memory-clobber bug somewhere in that.
> I'm not sure what you mean by 'nonstandard code,' could
Tom Lane wrote:
Geoffrey <[EMAIL PROTECTED]> writes:
Problem is, we seem to be having a problem with this reset issue and I
don't see a correlation in the backtraces. Most of them are in fact
related to inserts, but there are at least three different tables
involved. There are also some wher
Geoffrey <[EMAIL PROTECTED]> writes:
> Problem is, we seem to be having a problem with this reset issue and I
> don't see a correlation in the backtraces. Most of them are in fact
> related to inserts, but there are at least three different tables
> involved. There are also some where an INSER
Tom Lane wrote:
It seems you've got a corrupt "compiled statements" data structure for
a plpgsql trigger function. Offhand this does not look like any of the
known post-7.4.7 bug fixes. Can you show us the source code for that
trigger?
Problem is, we seem to be having a problem with this res
Geoffrey <[EMAIL PROTECTED]> writes:
> Program terminated with signal 11, Segmentation fault.
> #0 exec_stmt (estate=0xfeff8a90, stmt=0x0) at pl_exec.c:928
> in pl_exec.c
> #0 exec_stmt (estate=0xfeff8a90, stmt=0x0) at pl_exec.c:928
> #1 0x0083f005 in exec_stmts (estate=0xfeff8a90, stmt
e there were significant fixes in 7.4.8. It's possible that this is
a known bug that has already been fixed.
--
Brandon Aiken
CS/IT Systems Engineer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey
Sent: Monday, September 18, 2006 10:06 AM
To:
Postgresql 7.4.7 (yes, I've been telling them we need to upgrade to the
latest 7.4)
Red Hat Enterprise Linux ES release 3
We are having problems with the postgresql server resetting and dropping
all user connections. There is a core file generated and I've attached
a backtrace. I'm about to
