From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Marques <martin@bugs.unl.edu.ar>
Cc: pgsql-sql@postgresql.org
Subject: Re: CONTEXT on PL/pgSQL
Date: Fri, 23 Apr 2004 10:18:33 -0400
Message-ID: <23173.1082729913@sss.pgh.pa.us> (raw)
In-Reply-To: <200404231018.51461.martin@bugs.unl.edu.ar>
References: <200404231018.51461.martin@bugs.unl.edu.ar>
Martin Marques <martin@bugs.unl.edu.ar> writes:
> I have a simple function made with PL/pgSQL and when I call it I get this in
> the logs:
> 2004-04-23 10:15:32 [30669] LOG: statement: SELECT nodoSuperior(22) AS sup
> 2004-04-23 10:15:32 [30669] LOG: statement: SELECT $1
> CONTEXT: PL/pgSQL function "nodosuperior" line 7 at assignment
log_statement currently logs everything the parser sees, which includes
SQL commands generated by plpgsql.
Arguably these facilities should be separated, but until someone
makes a serious effort to provide plpgsql debugging features,
it's likely that nothing will be done about it. Right now this is
almost the only technique available for seeing what's going on inside
a plpgsql function, and crummy as it is, it's better than nothing...
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, martin@bugs.unl.edu.ar
Subject: Re: CONTEXT on PL/pgSQL
In-Reply-To: <23173.1082729913@sss.pgh.pa.us>
* 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