Re: CONTEXT on PL/pgSQL
От | Martin Marques |
---|---|
Тема | Re: CONTEXT on PL/pgSQL |
Дата | |
Msg-id | 200404231207.35886.martin@bugs.unl.edu.ar обсуждение исходный текст |
Ответ на | Re: CONTEXT on PL/pgSQL (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: CONTEXT on PL/pgSQL
|
Список | pgsql-sql |
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 -----------------------------------------------------------------
В списке pgsql-sql по дате отправления: