Re: ERROR: invalid memory alloc request size - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: ERROR: invalid memory alloc request size
Date
Msg-id 20051027162313.GA15335@surnet.cl
Whole thread Raw
In response to Re: ERROR: invalid memory alloc request size  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ERROR: invalid memory alloc request size
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:

> > I confess being attracted to Martijn's idea of looping until the correct
> > answer is obtained.  I don't think it's even too difficult to implement.
> > But I wonder if there's some hidden pitfall.
> 
> I've been looking at that and I think it can work.  The key point is
> that GetNewMultiXactId() does guarantee that space has been allocated
> for the new mxact's offset before it releases the lock (else we'd risk
> trying to read a nonexistent slru page when we fetch the offset in
> GetMultiXactIdMembers).

The remaining question for me is, how do we sleep until the correct
offset has been stored?

-- 
Alvaro Herrera                        http://www.advogato.org/person/alvherre
"Nunca se desea ardientemente lo que solo se desea por razón" (F. Alexandre)


pgsql-hackers by date:

Previous
From: Matteo Beccati
Date:
Subject: Re: ERROR: invalid memory alloc request size
Next
From: Tom Lane
Date:
Subject: Re: ERROR: invalid memory alloc request size