Postgres Pro
Downloads
Home   >   mailing lists

Re: PATCH: Handling too many notices from the debugging function - Mailing list pgadmin-hackers

From Dave Page
Subject Re: PATCH: Handling too many notices from the debugging function
Date
Msg-id CA+OCxox+CycSsF-v5PMC+C8U7kbGpJJOGiGAEQ4m0=ZNE=Ur7A@mail.gmail.com
Whole thread Raw
In response to PATCH: Handling too many notices from the debugging function  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Responses Re: PATCH: Handling too many notices from the debugging function  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
List pgadmin-hackers
Tree view
Thanks - patch applied, with a minor change reducing the timer delay to 100ms. Let me know if you see a problem with that.


On Fri, Jul 5, 2013 at 9:37 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
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.linkedin.com/in/asheshvashi




--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: pgAdmin III commit: If the function, which is being debugged, raise too
Next
From: Dave Page
Date:
Subject: pgAdmin III commit: Only attempt to cancel query threads that are actua