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 084759DCCBE for ; Tue, 31 Jan 2006 00:38:28 -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 62908-02 for ; Tue, 31 Jan 2006 00:38:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by postgresql.org (Postfix) with ESMTP id 990899DCCBD for ; Tue, 31 Jan 2006 00:38:25 -0400 (AST) Received: (qmail 19090 invoked from network); 31 Jan 2006 04:38:24 -0000 Received: from dsl081-105-229.den1.dsl.speakeasy.net (HELO [64.81.105.229]) (sribe@[64.81.105.229]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 31 Jan 2006 04:38:24 -0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Mon, 30 Jan 2006 21:38:23 -0700 Subject: Re: regarding debugging? From: Scott Ribe To: AKHILESH GUPTA , Postgres General Message-ID: Thread-Topic: [GENERAL] regarding debugging? Thread-Index: AcYmICsRaZDU05ITEdqtqAAUUQPXGA== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.16 required=5 tests=[AWL=0.160] X-Spam-Score: 0.16 X-Spam-Level: X-Archive-Number: 200601/1624 X-Sequence-Number: 90569 > 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