> El Vie 23 Abr 2004 11:18, Tom Lane escribió: > >>Martin Marques <[EMAIL PROTECTED]> 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?
U'r right, you can get rid of that CONTEXT configuring postgresql with
log_error_verbosity = terse
Regards Gaetano Mendola
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
