| From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | PATCH: Handling too many notices from the debugging function |
| Date: | 2013-07-05 08:37:09 |
| Message-ID: | CAG7mmowyGF-OOubCEgr2k+Y1zxZM5i+FgzFJ2E_oWMVTV-MEJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Dave,
During testing of debugger in pgAdmin III, EnterpriseDB's QA found one more
bug.
If the function, which is being debugged, raise too many notices, pgadmin
will become unresponsive.
As wxTextCtrl is not able to cop up with frequent AppendText calls, I have
to introduce a timer to show the
current message(s) after the timer stops. That allows to avoid the frequent
call to the AppendText function.
Appending those message to the current message instead of calling the
function.
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com>
*http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi>
| Attachment | Content-Type | Size |
|---|---|---|
| too_many_frequent_notices_debugger.patch | application/octet-stream | 4.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2013-07-05 09:11:17 | PATCH: Wait for the thread only if it is running |
| Previous Message | Ashesh Vashi | 2013-07-05 07:14:02 | PATCH: Handle the cross type of debugging (context & in-context) on same function at the same time |