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: 28 Oct 2005 12:36:48 -0400
- Message-id: <87irvh1tun(dot)fsf(at)stark(dot)xeocode(dot)com>
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
Home |
Main Index |
Thread Index