From: Martin Marques <martin@bugs.unl.edu.ar>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: CONTEXT on PL/pgSQL
Date: Fri, 23 Apr 2004 12:07:35 -0300
Message-ID: <200404231207.35886.martin@bugs.unl.edu.ar> (raw)
In-Reply-To: <23173.1082729913@sss.pgh.pa.us>
References: <200404231018.51461.martin@bugs.unl.edu.ar>
<23173.1082729913@sss.pgh.pa.us>
El Vie 23 Abr 2004 11:18, Tom Lane escribió:
> 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...
So the CONTEXT line just tells where the statement was made?
--
12:06:01 up 45 days, 16:30, 2 users, load average: 0.50, 0.46, 0.45
-----------------------------------------------------------------
Martín Marqués | select 'mmarques' || '@' || 'unl.edu.ar'
Centro de Telematica | DBA, Programador, Administrador
Universidad Nacional
del Litoral
-----------------------------------------------------------------
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: martin@bugs.unl.edu.ar, tgl@sss.pgh.pa.us
Subject: Re: CONTEXT on PL/pgSQL
In-Reply-To: <200404231207.35886.martin@bugs.unl.edu.ar>
* 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