>>>>> "Kevin" == Kevin Brown <[EMAIL PROTECTED]> writes:
>> The bigger problem though with this is that it makes the
>> problem of list overflow much worse. The hard part about
>> shared memory management is not so much that the available
>> space is small, as that the available space is fixed --- we
>> can't easily change it after postmaster start. The more finely
Again, I can suggest the shared memory MemoryContext we use in
TelegraphCQ that is based on the OSSP libmm memory manager. We use it
to grow and shrink shared memory at will.
--
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
