Re: [HACKERS] Re: alloca (was: Postgres Speed or lack thereof)

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: alloca (was: Postgres Speed or lack thereof)
Date: 1999-01-25 16:23:25
Message-ID: 36AC9A7D.23BD013E@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1999-01-25 16:25:16 Re: [HACKERS] Re: datetime regress test busted by incomplete checkin
Previous Message Oleg Broytmann 1999-01-25 16:13:32 Re: [HACKERS] Re: datetime regress test busted by incomplete checkin