Обсуждение: PATCH: Wait for the thread only if it is running

Поиск
Список
Период
Сортировка

PATCH: Wait for the thread only if it is running

От
Ashesh Vashi
Дата:
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.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi

Вложения

Re: PATCH: Wait for the thread only if it is running

От
Ashesh Vashi
Дата:
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.vashi@enterprisedb.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.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




--
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi

Вложения

Re: PATCH: Wait for the thread only if it is running

От
Dave Page
Дата:
Thanks - patch applied.


On Mon, Jul 8, 2013 at 6:03 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
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.vashi@enterprisedb.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.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




--
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi



--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.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

Re: PATCH: Wait for the thread only if it is running

От
Ashesh Vashi
Дата:
Thanks

On Mon, Jul 8, 2013 at 7:18 PM, Dave Page <dpage@pgadmin.org> wrote:
Thanks - patch applied.


On Mon, Jul 8, 2013 at 6:03 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
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.vashi@enterprisedb.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.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




--
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi



--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.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



--
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi