| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-27 16:23:13 |
| Message-ID: | 20051027162313.GA15335@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
> 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-27 16:27:08 | Re: ERROR: invalid memory alloc request size <a_big_number_here> |
| Previous Message | Matteo Beccati | 2005-10-27 16:16:24 | Re: ERROR: invalid memory alloc request size <a_big_number_here> |