From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Fixed crash in execution dialog |
Date: | 2013-07-26 12:57:40 |
Message-ID: | CA+OCxoyAff5MSYWaEYJNAp=gBoQnE6wHAKA1QvroEaBdwKmCyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Thanks, patch applied.
On Fri, Jul 26, 2013 at 8:53 AM, Akshay Joshi
<akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
> Hi Dave
>
> Today I have fixed one crash in execution dialog. The bug is reproducible by
> performing following steps:
>
> Connect to any database server.
> Right click on the database(big in size) and select maintenance.
> Start taking maintenance and click the cancel button.
> After clicking on cancel, immediately click on cross (x) button.
>
> With the above steps Abort() function gets called twice on from cancel event
> and another from close event. Attached is the patch file. Please review it
> and if it looks good to you then can you please commit it.
>
> --
> Akshay Joshi
> Senior Software Engineer
> EnterpriseDB Corporation
> The Enterprise PostgreSQL Company
> Phone: +91 20-3058-9522
> Mobile: +91 976-788-8246
>
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>
--
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 | 2013-07-26 14:13:39 | pgAdmin III commit: Add support for event triggers in 9.3+. |
Previous Message | Dave Page | 2013-07-26 12:57:04 | pgAdmin III commit: Keep better track of when external process threads |