From: SunWuKung <Balazs.Klein@axelero.hu>
To: pgsql-general@postgresql.org
Subject: Re: regarding debugging?
Date: Fri, 3 Feb 2006 21:27:45 +0100
Message-ID: <MPG.1e4ddb296e3fdb9f98968c@news.postgresql.org> (raw)
References: <ad39daf90601292238k2b1ff604r3aab7822fea0f998@mail.gmail.com>
<C00437CF.3F9D0%scott_ribe@killerbytes.com>
In article <C00437CF.3F9D0%scott_ribe@killerbytes.com>,
scott_ribe@killerbytes.com says...
> > 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
>
>
>
EMS Postgresql Manager has a debugger in it. Its not perfect but still
it is quite useful.
B.
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: Balazs.Klein@axelero.hu, pgsql-general@postgresql.org
Subject: Re: regarding debugging?
In-Reply-To: <MPG.1e4ddb296e3fdb9f98968c@news.postgresql.org>
* 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