X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 2CBB79DC9F7 for ; Fri, 3 Feb 2006 16:28:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68839-02 for ; Fri, 3 Feb 2006 16:27:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 4C31E9DC816 for ; Fri, 3 Feb 2006 16:27:53 -0400 (AST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 9844E30945; Fri, 3 Feb 2006 21:27:53 +0100 (MET) From: SunWuKung X-Newsgroups: pgsql.general Subject: Re: regarding debugging? Date: Fri, 3 Feb 2006 21:27:45 +0100 Organization: Nirvana Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: MicroPlanet-Gravity/2.60.2060 To: pgsql-general@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.144 required=5 tests=[AWL=0.144] X-Spam-Score: 0.144 X-Spam-Level: X-Archive-Number: 200602/151 X-Sequence-Number: 90816 In article , 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.