Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
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)
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2005-10-27 16:27:08|
|Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here> |
|Previous:||From: Matteo Beccati||Date: 2005-10-27 16:16:24|
|Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here>|