| From: | Matteo Beccati <php(at)beccati(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:16:24 |
| Message-ID: | 4360FD58.4000506@beccati.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
>> I don't see any easy way to fix this except by introducing a lot more
>> locking than is there now --- ie, holding the MultiXactGenLock until the
>> new mxact's starting offset has been written to disk. Any better ideas?
>
> Well, it isn't a very good solution because it requires us to retain the
> MultiXactGenLock past a XLogInsert and some I/O on SLRU pages.
> Previously the lock was mostly only used in short operations and very
> rarely held during I/O. But I don't see any other solution either.
> Patch attached.
The patch works wonderfully. I'm trying to stress the whole app and with
no errors until now.
> Thanks to Matteo for finding the bug!
Thanks to you all for helping out and fixing it :)
Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-10-27 16:23:13 | Re: ERROR: invalid memory alloc request size <a_big_number_here> |
| Previous Message | Tom Lane | 2005-10-27 16:08:47 | Re: ERROR: invalid memory alloc request size <a_big_number_here> |