pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedregarding debugging?
4+ messages / 4 participants
[nested] [flat]
* regarding debugging?
@ 2006-01-30 06:38 AKHILESH GUPTA <akhilesh.davim@gmail.com>
2006-01-31 04:38 ` Re: regarding debugging? Scott Ribe <scott_ribe@killerbytes.com>
2006-02-08 17:36 ` Re: regarding debugging? BigSmoke <bigsmoke@gmail.com>
0 siblings, 2 replies; 4+ messages in thread
From: AKHILESH GUPTA @ 2006-01-30 06:38 UTC (permalink / raw)
To: pgsql-general@postgresql.org; pgsql-sql
hi all,
i have a query regarding debbuging in PGSQL.
just like there is a debugger in C/C++, 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?
thanks in advance................................................!!
(waiting for your response)
--
Thanks & Regards,
Akhilesh
DAV Institute of Management
Faridabad(Haryana)
GSM:-(+919891606064)
(+911744293789)
"FAILURES CAN BE FORGIVEN BUT AIMING LOW IS A CRIME"
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: regarding debugging?
2006-01-30 06:38 regarding debugging? AKHILESH GUPTA <akhilesh.davim@gmail.com>
@ 2006-01-31 04:38 ` Scott Ribe <scott_ribe@killerbytes.com>
2006-02-03 20:27 ` Re: regarding debugging? SunWuKung <Balazs.Klein@axelero.hu>
1 sibling, 1 reply; 4+ messages in thread
From: Scott Ribe @ 2006-01-31 04:38 UTC (permalink / raw)
To: AKHILESH GUPTA <akhilesh.davim@gmail.com>; Postgres General <pgsql-general@postgresql.org>
> 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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: regarding debugging?
2006-01-30 06:38 regarding debugging? AKHILESH GUPTA <akhilesh.davim@gmail.com>
2006-01-31 04:38 ` Re: regarding debugging? Scott Ribe <scott_ribe@killerbytes.com>
@ 2006-02-03 20:27 ` SunWuKung <Balazs.Klein@axelero.hu>
0 siblings, 0 replies; 4+ messages in thread
From: SunWuKung @ 2006-02-03 20:27 UTC (permalink / raw)
To: pgsql-general@postgresql.org
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: regarding debugging?
2006-01-30 06:38 regarding debugging? AKHILESH GUPTA <akhilesh.davim@gmail.com>
@ 2006-02-08 17:36 ` BigSmoke <bigsmoke@gmail.com>
1 sibling, 0 replies; 4+ messages in thread
From: BigSmoke @ 2006-02-08 17:36 UTC (permalink / raw)
To: pgsql-sql
Checking how your PgSQL statements are executed, can be done using
EXPLAIN [1].
EXPLAIN ANALYZE will also execute (but not dry-run!) your statement.
I work with a seperate development and production database. Once the
changes to the schema in the development DB are done, I commit them to
the production DB using ActiveRecord migrations. You could do the same
with an advanced schema diff tool such as pgdiff [2] or zongle [3].
- Rowan
[1] http://www.postgresql.org/docs/current/interactive/sql-explain.html
[2] http://pgdiff.sourceforge.net/
[3] http://zongle.sourceforge.net/
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2006-02-08 17:36 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-01-30 06:38 regarding debugging? AKHILESH GUPTA <akhilesh.davim@gmail.com>
2006-01-31 04:38 ` Scott Ribe <scott_ribe@killerbytes.com>
2006-02-03 20:27 ` SunWuKung <Balazs.Klein@axelero.hu>
2006-02-08 17:36 ` BigSmoke <bigsmoke@gmail.com>
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