Re: [RFC] obtaining the function call stack - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [RFC] obtaining the function call stack
Date
Msg-id 27995.1247511737@sss.pgh.pa.us
Whole thread Raw
In response to [RFC] obtaining the function call stack  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [RFC] obtaining the function call stack  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: [RFC] obtaining the function call stack  (decibel <decibel@decibel.org>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> So, the idea is to have a stack maintained by the function manager; each
> called function enters an element in it containing the interesting
> information about the function.  We'd have another function that would
> return this stack as a result set.  (With this arrangement, the topmost
> element would always appear to be this "peek" function.)

> I haven't looked at the code to see how this would actually be
> implemented, so I don't have more details to offer.  Does anybody have
> opinions on the matter?

The performance and error recovery implications are unfavorable.
Just how badly do you need this, and for what?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: [RFC] obtaining the function call stack
Next
From: "Kevin Grittner"
Date:
Subject: Re: Predicate migration on complex self joins