On Fri, Mar 07, 2008 at 10:15:57AM -0800, Kevin Lindsay wrote:
> Great, thanks Clint, I'll submit to the forum.
Thank you.
http://forums.oracle.com/forums/thread.jspa?threadID=627401&tstart=0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAI
On Fri, Mar 07, 2008 at 09:34:24AM -0500, Clint Adams wrote:
> On Wed, Mar 05, 2008 at 09:10:08PM -0800, Kevin Lindsay wrote:
> > I have not yet reported this to upstream. Please let me know if you will be
> > doing this or if I can help out in anyway.
>
> Actually, if you can stand to use a web
On Wed, Mar 05, 2008 at 09:10:08PM -0800, Kevin Lindsay wrote:
> I have not yet reported this to upstream. Please let me know if you will be
> doing this or if I can help out in anyway.
Actually, if you can stand to use a web forum, sending the patch to
http://forums.oracle.com/forums/forum.jspa?
On Wed, Mar 05, 2008 at 09:10:08PM -0800, Kevin Lindsay wrote:
> I have not yet reported this to upstream. Please let me know if you will be
> doing this or if I can help out in anyway.
Should be in progress.
> --- db-4.6.21.orig/mp/mp_fmethod.c2007-06-01 16:30:30.0 +
> +++ db-4.6
Package: libdb4.6
Severity: normal
Tags: patch
Currently it is not possible to set an in-memory database's maxium size using
it's memory pool's set_maxsize() function. Calling this function after a
db_open will cause libdb to hang in a mutex deadlock. This has only been
tested on an in-memory data
5 matches
Mail list logo
