Re: PATCH: Handling too many notices from the debugging function

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: Handling too many notices from the debugging function
Date: 2013-07-08 13:44:32
Message-ID: CA+OCxox+CycSsF-v5PMC+C8U7kbGpJJOGiGAEQ4m0=ZNE=Ur7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

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(dot)vashi(at)enterprisedb(dot)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.enterprisedb.com>
>
>
>
> *http://www.linkedin.com/in/asheshvashi*<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

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2013-07-08 13:47:57 pgAdmin III commit: Only attempt to cancel query threads that are actua
Previous Message Dave Page 2013-07-08 13:43:54 pgAdmin III commit: If the function, which is being debugged, raise too