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

From Thomas G. Lockhart
Subject Re: [HACKERS] Re: alloca (was: Postgres Speed or lack thereof)
Date
Msg-id 36AC9A7D.23BD013E@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] Re: alloca (was: Postgres Speed or lack thereof)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Right, storage allocated by alloca is part of the calling function's
> stack frame --- it goes away when that function exits, no sooner and
> no later.

And as I'm sure many already know, there are limits on stack frame size
on many architectures, and limits on total stack size on every platform.
The available size is not in the same league as malloc()-style heap
allocation.
                   - Tom


pgsql-hackers by date:

Previous
From: Oleg Broytmann
Date:
Subject: Re: [HACKERS] Re: datetime regress test busted by incomplete checkin
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Re: datetime regress test busted by incomplete checkin