Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: ERROR: invalid memory alloc request size <a_big_number_here>


  • From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
  • To: Matteo Beccati <php(at)beccati(dot)com>
  • Cc: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here>
  • Date: Thu, 27 Oct 2005 11:16:19 +0200
  • Message-id: <20051027091618(dot)GC4259(at)svana(dot)org>

On Thu, Oct 27, 2005 at 10:59:30AM +0200, Matteo Beccati wrote:
> Hi,
> 
> I'm using 8.1beta4 on a development server for a rather db-intensive 
> application. This application has a multiprocess daemon which was 
> working fairly well in past. After some recent changes I started having 
> deadlock problems. While investigating to remove what was causing them I 
> removed some FOR UPDATE clauses (added on 8.0 to prevent other deadlock 
> situations), hoping that the newly added FK share locks would better 
> handle the concurrent access. In fact the deadlock errors went away, but 
> I suddenly started getting some of these:

Backtrace would be nice. I don't suppose your backend is compiled with
debugging? If so, try attaching to the backend and do:

break MemoryContextAlloc if size > 1000000000

Obviously something is trying to allocate and negative number of
bytes... 4291419108 = -3548188

Hope this helps,
-- 
Martijn van Oosterhout   <kleptog(at)svana(dot)org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

Attachment: pgpKd1GfJVAxa.pgp
Description: PGP signature



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group