Re: [RFC] obtaining the function call stack

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [RFC] obtaining the function call stack
Date: 2009-07-13 21:02:51
Message-ID: 3073cc9b0907131402t380becf3i45ea3f705e4e502f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 13, 2009 at 4:00 PM, A.M.<agentm(at)themactionfaction(dot)com> wrote:
>
> How would I go about generating a meaningful backtrace for a plpgsql
> function that calls a plperl function? One would also expect a C function
> which calls a plpgsql function to appear, too, no? Shouldn't there be a
> unified backtrace subsystem?
>

i guess, that is what Alvaro is suggesting

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jamie Fox 2009-07-13 21:13:37 large object does not exist after pg_migrator
Previous Message A.M. 2009-07-13 21:00:21 Re: [RFC] obtaining the function call stack