Re: Recommendations on plpgsql debugger?
От | Gauthier, Dave |
---|---|
Тема | Re: Recommendations on plpgsql debugger? |
Дата | |
Msg-id | 0AD01C53605506449BA127FB8B99E5E161126253@FMSMSX105.amr.corp.intel.com обсуждение исходный текст |
Ответ на | Recommendations on plpgsql debugger? (Chris Travers <chris.travers@gmail.com>) |
Список | pgsql-general |
One thing I've done in the past is to create a temporary table and insert "raise notice" debug statements to it, incrementing a sequence as it went along. Then just select the message with order by the seq. Useful in the recursive calls I was testing at the time. But it did require that I stick a bunch of "raise notice" statements and reload the procedure(s).
But ya, a real debugger sould be great.
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Chris Travers
Sent: Tuesday, January 15, 2013 3:00 AM
To: Postgres General
Subject: [GENERAL] Recommendations on plpgsql debugger?
Hi all;
I have a client who needs a way to step through a PL/PGSQL function and ideally see what one is doing at present. I noticed that there used to be an EDB Debugger module for this purpose but I can't seem to find one for 9.1 and I can't seem to pull from csv to try.
Any alternatives? Am I missing something?
Best Wishes,
Chris Travers
В списке pgsql-general по дате отправления: