[Pgpool-general] Large insert queries

[Lee Smith]

Even with the patches applied there still seems to be lots of issues with the memory pooling (and large blocks).  I still see random crashes, even with a small query, so somewhere things are getting messed up.  I'm going to look into it further once I get a chance, but for now its just not stable enough to use.  Are there any benchmarks for performance on the savings of not having to ask libc for memory?  I was under the impression that libc had some form of caching allocations already.  For now I have just disabled it by redefining the stuff in pool_memory.h:

#define palloc(s) malloc((s))
#define repalloc(p, s) realloc( (p),(s))
#define pfree(p) free( (p) )
#define pstrdup(s) strdup((s))
#define palloc0(s) calloc( (s), 1)



----- Original Message -----
From: Yoshiyuki Asaba <y-asaba at sraoss.co.jp>
To: lee smith <lee.smith at aionex.com>
Cc: pgpool-general at pgfoundry.org
Sent: Thursday, November 9, 2006 9:53:35 PM GMT-0600 US/Central
Subject: Re: [Pgpool-general] Large insert queries

Hi,

From: Lee Smith <lee.smith at aionex.com>
Subject: Re: [Pgpool-general] Large insert queries
Date: Thu, 9 Nov 2006 13:18:49 -0800 (PST)

> After some more investigation, I've located another issue; however
> fixing this one seems to clear up any crashing, although it's
> probably leaking memory now (or something worse).

Thank you for the report. I saw SIGSEGV in the following code.

  void *x;
  x = palloc(8192);

I've committed the fix and your NULL checking patch.

Regards,
--
Yoshiyuki Asaba
y-asaba at sraoss.co.jp