From: Marcin Stępnicki <mstepnicki@gmail.com>
To: Dean Rasheed <dean_rasheed@hotmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow set-returning functions
Date: Sun, 27 Jan 2008 20:16:20 +0100
Message-ID: <1201461380.19607.6.camel@localhost> (raw)
In-Reply-To: <BAY113-W336D429DFB9A2E2772E906F23B0@phx.gbl>
References: <BAY113-W283034364555E644CD1765F23C0@phx.gbl>
<47935C0C.4090908@enterprisedb.com>
<b42b73150801200725y45600f6end8d234cea4f8ff22@mail.gmail.com>
<10405.1200853835@sss.pgh.pa.us>
<BAY113-W336D429DFB9A2E2772E906F23B0@phx.gbl>
Dnia 27-01-2008, N o godzinie 17:29 +0000, Dean Rasheed pisze:
> The CONTEXT is very useful, particularly when functions call other
> functions, since it gives the call stack (presumably only for SQL and
> PL/pgSQL functions). For top-level queries I would ideally like the
> CONTEXT to log the SQL being executed, but I couldn't figure out how
> to access that information.
>
> Anyway, I'd be interested to know if anyone has thought about doing
> anything like this before and if anyone else might find this useful.
>
> Dean
I'd love to see that. The mentioned PREPARE workaround doesn't seem to
work when executed function calls for example three another (or I don't
know how to use it in such situation) - and is generally painful to
use.
I'm afraid I can't help you much (besides testing) but I'd be more than
interested in such improvement.
Regards,
Marcin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mstepnicki@gmail.com, dean_rasheed@hotmail.com
Subject: Re: Slow set-returning functions
In-Reply-To: <1201461380.19607.6.camel@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox