From: | "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com> |
---|---|
To: | "Aaron Bono" <postgresql(at)aranya(dot)com>, "Postgres SQL language list" <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Logging in Stored Procedure |
Date: | 2006-07-13 00:10:38 |
Message-ID: | 71E37EF6B7DCC1499CEA0316A256832802B3E282@loki.wc.globexplorer.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Well, perhaps the NOTICE functionality, e.g.
RAISE NOTICE ''report id of % for date %'', rpt_rec.report_id, rpt_rec.report_s_date;
This will show on the terminal if running from a console, and also writes to the log, IIRC. See the documentation for your version for details.
HTH,
Greg Williamson
DBA
GlobeXplorer LLC
-----Original Message-----
From: pgsql-sql-owner(at)postgresql(dot)org on behalf of Aaron Bono
Sent: Wed 7/12/2006 4:28 PM
To: Postgres SQL language list
Cc:
Subject: [SQL] Logging in Stored Procedure
OK, maybe a stupid simple question but, how do you add logging to a stored
procedure? My procedure is running but the results I get are not complete
and I need to see better what is going wrong. The tool I use has a debugger
but the debugger is barfing at a particular line that, when run without the
debugger, works with no errors so I know there is something wrong with the
debugger.
Thanks,
Aaron
--
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.com
==================================================================
!DSPAM:44b58e5178651804284693!
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2006-07-13 01:48:28 | Re: Unexpected SQL error for UPDATE |
Previous Message | Aaron Bono | 2006-07-12 23:28:42 | Logging in Stored Procedure |