From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: Wait for the thread only if it is running |
Date: | 2013-07-08 05:03:46 |
Message-ID: | CAG7mmowGiewOQ=1nUyA_4rJvzK6TAna0WOnkoQ7AyKVTVD_25A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Found couple of more issues in the same area.
- Forgot to set variable to NULL after deleting it
- Removed redundant code
- Canceling the thread execution only if the thread is running
Attached is the updated patch.
On Fri, Jul 5, 2013 at 2:41 PM, Ashesh Vashi
<ashesh(dot)vashi(at)enterprisedb(dot)com>wrote:
> Hi,
>
> I have modified the code a little bit for the ctlSQLResult and debugger,
> so that it will wait for the thread only if it was running.
> It should resolve the issue reported in the following mail thread.
> http://www.postgresql.org/message-id/E7BD3DF3326743FC867EDDB5D2446840@O
>
> --
>
> 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>
>
--
--
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 |
---|---|---|
Wait_only_if_thread_running_v2.patch | application/octet-stream | 3.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2013-07-08 12:34:38 | pgAdmin III commit: Use a modified icon to indicate materialised views. |
Previous Message | Ashesh Vashi | 2013-07-08 04:32:37 | PATCH: Debug a function deleted outside the pgAdmin III environment |