Re: server resetting

From: Geoffrey <esoteric(at)3times25(dot)net>
To: PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: server resetting
Date: 2006-09-19 01:06:35
Message-ID: 450F429B.9040309@3times25.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Geoffrey <esoteric(at)3times25(dot)net> 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 you expand on
>> that?
>
> The traces include code from /usr/local/lib/libgrid.so and
> /usr/local/lib/libpcmsrv.so ... I don't know what those are,
> but I'm quite sure they are not invoked by a standard Postgres build.
> I also find it suggestive that they appear to have been written in C++
> ... we've seen problems before from trying to link C++ code into the
> backend, because it tends to bring along its own incompatible ideas
> about how to do error recovery and memory management.

The libpcmsrv is a library for looking up miles, vendor provided. I'll
have to check on the other one, it may be related to the same package.

Thanks for the heads up on C++ code.

It seems we may have located a memory problem in a library that is used
throughout our code, thus, we are looking into this at this time.

Thanks again.

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2006-09-19 01:48:20 Re: duplicate key violates unique constraint
Previous Message Jeff Davis 2006-09-19 00:25:13 Re: duplicate key violates unique constraint