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

Re: BUG #5675: out of memory at request size 32Mb

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5675: out of memory at request size 32Mb
Date: 2010-09-24 14:37:17
Message-ID: 4C9CB79D.8090300@pse-consulting.de (view raw or flat)
Thread:
Lists: pgsql-bugs
  Am 24.09.10 14:54, schrieb Robert Haas:
> On Fri, Sep 24, 2010 at 8:42 AM, Andreas Pflug
> <pgadmin(at)pse-consulting(dot)de>  wrote:
>> The following bug has been logged online:
>>
>> Bug reference:      5675
>> Logged by:          Andreas Pflug
>> Email address:      pgadmin(at)pse-consulting(dot)de
>> PostgreSQL version: 8.4.4
>> Operating system:   Linux 2.6.26 i686
>> Description:        out of memory at request size 32Mb
>> Details:
>>
>> A slony 2.0 cluster running for a year, no config changes lately. Slony has
>> to replicate a table with a bytea column; maximum so far was a little over
>> 32MB.
>>
>> Lately, the slave's slon process fails to replicate. The server reports "out
>> of memory", "Failed on request of size 33554432.". The slon log shows an
>> insert was the failing statement, the server log spits out its memory
>> contexts but not the failing statement.
>>
>> One log line that catched my attention was
>> MessageContext: 485902696 total in 6 blocks; 32160 free (16 chunks);
>> 485870536 used
>> which is well beyond the configured memory limits (280MB shared_buffers,
>> temp 32MB, workmem 64MB)
> Are you sure you meant to report this here?  Seems likely to be a
> Slony issue, although of course I'm not sure of that.
>
It's the postgres server that reports the oom situation on the insert query.

On further invesigation, the slon process (running on the same machine) 
consumed all memory on the 144MB-Insert (for a 29MB column) making pgsql 
bail out.

Regards,
Andreas



In response to

pgsql-bugs by date

Next:From: Andrew DunstanDate: 2010-09-24 14:42:48
Subject: Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Previous:From: Magnus HaganderDate: 2010-09-24 14:15:08
Subject: Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group