| From: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
|---|---|
| To: | AKHILESH GUPTA <akhilesh(dot)davim(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: regarding debugging? |
| Date: | 2006-01-31 04:38:23 |
| Message-ID: | C00437CF.3F9D0%scott_ribe@killerbytes.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
> where we can check the execution of our program or we can dry run our code, is
> there aby option or feature with PGSQL for the same purpose that we can check
> our PGSQL statements?
No, unfortunately not. What I do is:
- error check everything you can, and use RAISE EXCEPTION with descriptive
error messages
- come up with test cases to exercise all branches of code
- print useful debugging info while tracking down problems
--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 665-7007 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeffrey W. Baker | 2006-01-31 04:41:22 | Re: New project launched : PostgreSQL GUI Installer for |
| Previous Message | jao | 2006-01-31 04:19:37 | Re: Insert rate drops as table grows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario Splivalo | 2006-01-31 09:51:51 | CREATE VIEW form stored in database? |
| Previous Message | AKHILESH GUPTA | 2006-01-30 06:38:54 | regarding debugging? |