| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: CONTEXT on PL/pgSQL |
| Date: | 2004-04-23 14:18:33 |
| Message-ID: | 23173.1082729913@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antal Attila | 2004-04-23 14:33:14 | Multi ordered select and indexing |
| Previous Message | Antal Attila | 2004-04-23 13:32:13 | Multi ordered select and indexing |