Re: Possible bug in plpgsql/src/gram.y
От | Bruce Momjian |
---|---|
Тема | Re: Possible bug in plpgsql/src/gram.y |
Дата | |
Msg-id | 200107120350.f6C3oQo20329@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Possible bug in plpgsql/src/gram.y (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
> Bruce Momjian <pgman@candle.pha.pa.us> writes: > > Also, can someone tell my why we use malloc in plpgsql? > > Plain palloc() won't do because the compiled tree for the function needs > to outlive the current query. However, malloc() is not cool. Really, > these structures ought to be built in a memory context created specially > for each function --- then it'd be possible to reclaim the memory if the > function is deleted or we realize we need to invalidate its compiled > tree. > > I've had this in mind to do for awhile, but haven't gotten to it. > Do you want to put it on TODO? Done: * Change PL/PgSQL to use palloc() instead of malloc() -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: