Re: alloca (was: Postgres Speed or lack thereof) - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: alloca (was: Postgres Speed or lack thereof)
Date
Msg-id Pine.BSF.4.05.9901261407060.94383-100000@thelab.hub.org
Whole thread Raw
In response to Re: alloca (was: Postgres Speed or lack thereof)  (Goran Thyni <goran@kirra.net>)
Responses Re: [HACKERS] Re: alloca (was: Postgres Speed or lack thereof)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


Before this patch is applied, havae we determined wheteher or not its even
a useful thing to pursue?  I thought the general conscious was that, for
us, it wasn't...
On Tue, 26 Jan 1999, Goran Thyni wrote:

> The Hermit Hacker wrote:
> > Make you a deal...
> > 
> > You build the code such that "#ifdef HAVE_ALLOCA" is true, so that those
> > platforms that either don't support it, or have broken suport for it,
> > aren't affect, and you are most welcome to work on it...
> 
> Yeah right, I should keep my mouth shut. :-)
> 
> It is a big job, starting getting with getting profiling working on 
> my box, analyzing lots of code and then come up with some optimations.
> 
> We can start with the patch below to detect alloca() in autoconf.
> 
>     best regards,
> -- 
> -----------------
> G�ran Thyni
> This is Penguin Country. On a quiet night you can hear Windows NT
> reboot!

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Goran Thyni
Date:
Subject: Re: alloca (was: Postgres Speed or lack thereof)
Next
From: lorenzo@argon.roma2.infn.it
Date:
Subject: dump doesn't save views and blobs