Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: ERROR: invalid memory alloc request size <a_big_number_here>


  • 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: Thu, 27 Oct 2005 16:15:23 -0400
  • Message-id: <23650(dot)1130444123(at)sss(dot)pgh(dot)pa(dot)us>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group