Re: realloc suggestion - Mailing list pgsql-hackers

From Karel Zak
Subject Re: realloc suggestion
Date
Msg-id Pine.LNX.3.96.1010123165549.10618B-100000@ara.zf.jcu.cz
Whole thread Raw
In response to Re: realloc suggestion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 22 Jan 2001, Tom Lane wrote:

> Karel Zak <zakkr@zf.jcu.cz> writes:
> >  I again a little look at aset code and I probably found small performance 
> > reserve in small chunks (chunk <= ALLOC_CHUNK_LIMIT) reallocation.
> 
> Hmm.  I wouldn't have thought that realloc got called often enough to be
> worth optimizing, but it does seem to get called a few hundred times
> during the regress tests, so maybe it's worth a little more code to do
> this.  (Looks like most of the realloc calls come from enlargeStringInfo
> while dealing with long query strings --- since in this case the string
> buffer is the only thing yet allocated in QueryContext, the special-case
> check wins.)
> 
> I've committed this change.  Thanks for the suggestion!
I love OpenSource and CVS source distribution model - only couple hours
between idea and official source change :-)
Karel



pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: Re: PL/Python (was: Re: [GENERAL] Re: Trigger)
Next
From: Tom Lane
Date:
Subject: Re: question