From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: To fix the issue in Debugger module (pgAdmin4) |
Date: | 2016-10-07 11:53:22 |
Message-ID: | CA+OCxowWbW6sYELhWiCGW3znKE6Fk19Hwuns8BzZHd94iqABnA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Fri, Oct 7, 2016 at 12:42 PM, Murtuza Zabuawala
<murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:
> Hi Dave,
>
> I faced the same issue when I initially tried that, but then as per Neel
> suggestion I changed SELECT pg_sleep() to PERFORM pg_sleep() in function.
> You will face the same in pgAdmin3 if you use select pg_sleep() in your
> function the debug call never returns from DB server.
In which case, doesn't that imply the debugger is missing critical
debug info? If I run the query in the query tool, I get:
====
INFO: EMPNO ENAME
INFO: ----- -------
ERROR: query has no destination for result data
HINT: If you want to discard the results of a SELECT, use PERFORM instead.
CONTEXT: PL/pgSQL function list_emp() line 11 at SQL statement
Query returned successfully in 2 secs.
====
It seems to me that the debugger should be able to give the same error.
Regardless of that, I'll test with PERFORM.
Thanks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2016-10-07 11:57:39 | pgAdmin 4 commit: Correctly identify server type upon first connection. |
Previous Message | Dave Page | 2016-10-07 11:49:10 | Re: [Patch][pgAdmin4]: RM#1577 - Debug option for function/procedure under package node |