Re: postgres database crashed

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: "Ashish Goel" <postgres_help(at)yahoo(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgres database crashed
Date: 2006-10-15 16:30:11
Message-ID: 1448.24.211.165.134.1160929811.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Did you follow Tom's suggestion of trying with a postgres configured with
--enable-cassert ?

cheers

andrew

Ashish Goel wrote:
> But the same code worked when I inserted around 2500 images in the
> database. After that it started crashing. So , I don't think it's because
> of error in the code. Can u suggest some other possible reasons and also
> why is it crashing at call to memcpy(). I have also checked the memory
> allocations , and i don't find problem there.
>
>
>
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: Ashish Goel
> writes:
>> We have a following table xyz( id int , fname varchar(50), img image)
>> where image is a data type we have created similar to lo.
>> ...
>> Can somebody suggest us what might be the cause of error and what can we
>> do to resolve it ?
>
> Incorrect code in your custom datatype, almost certainly. Check
> computations of memory size allocations, for example. Test it in
> a backend compiled with --enable-cassert.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2006-10-15 16:30:45 Re: more anti-postgresql FUD
Previous Message Simon Riggs 2006-10-15 16:22:33 Re: index advisor