From: | Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: CONTEXT on PL/pgSQL |
Date: | 2004-04-23 15:07:35 |
Message-ID: | 200404231207.35886.martin@bugs.unl.edu.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
El Vie 23 Abr 2004 11:18, Tom Lane escribió:
> Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)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
-----------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2004-04-23 16:41:21 | Re: Multi ordered select and indexing |
Previous Message | Antal Attila | 2004-04-23 14:33:14 | Multi ordered select and indexing |