Re: ERROR: invalid memory alloc request size <a_big_number_here>
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Greg Stark <gsstark(at)mit(dot)edu>
- 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: Fri, 28 Oct 2005 12:40:55 -0400
- Message-id: <2750(dot)1130517655(at)sss(dot)pgh(dot)pa(dot)us>
Greg Stark <gsstark(at)mit(dot)edu> writes:
> 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.
Well, the whole idea didn't work anyway :-(. But I think your proposal
is equivalent to holding the lock throughout CreateMultiXactId, which is
exactly what we're trying to avoid doing ...
regards, tom lane
Home |
Main Index |
Thread Index