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

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

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>,Matteo Beccati <php(at)beccati(dot)com>,Martijn van Oosterhout <kleptog(at)svana(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here>
Date: 2005-10-28 16:36:48
Message-ID: 87irvh1tun.fsf@stark.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> creatingOffsetZero will be a bool that gets set before releasing
> MultiXactGenLock if offset 0 is being returned, and then we clear it
> after updating the slru data structures if we had starting offset 0.

If you're going to have a special flag indicating this couldn't you just have
a special flag indicating that the offset isn't ready yet? Loop until that
flag is cleared instead of looking for offset != 0 at all.

-- 
greg


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-10-28 16:40:55
Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here>
Previous:From: Matteo BeccatiDate: 2005-10-28 16:25:59
Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here>

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