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: | 2005-10-27 20:15:23 |
Message-ID: | 23650.1130444123@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> We'd have to make sure zero is never the *correct* value of the offset,
>> but that just means wasting one word, which seems no problem.
> In theory it's possible for only half the word to be written or even to have
> outright garbage show up. In practice I think there are no actual
> architectures where this can really happen though.
Not an issue, because we have a lock around the read or write of the
slru buffer page. The problem is that there's no lock continuously held
through the creation of a multixact entry, and we don't really wish to
add one ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-10-27 20:46:03 | Re: enums |
Previous Message | Greg Stark | 2005-10-27 20:10:57 | Re: ERROR: invalid memory alloc request size <a_big_number_here> |