From: Scott Ribe <scott_ribe@killerbytes.com>
To: AKHILESH GUPTA <akhilesh.davim@gmail.com>
To: Postgres General <pgsql-general@postgresql.org>
Subject: Re: regarding debugging?
Date: Mon, 30 Jan 2006 21:38:23 -0700
Message-ID: <C00437CF.3F9D0%scott_ribe@killerbytes.com> (raw)
In-Reply-To: <ad39daf90601292238k2b1ff604r3aab7822fea0f998@mail.gmail.com>
> 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@killerbytes.com
http://www.killerbytes.com/
(303) 665-7007 voice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: scott_ribe@killerbytes.com, akhilesh.davim@gmail.com, pgsql-general@postgresql.org
Subject: Re: regarding debugging?
In-Reply-To: <C00437CF.3F9D0%scott_ribe@killerbytes.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox