From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | PATCH: Wait for the thread only if it is running |
Date: | 2013-07-05 09:11:17 |
Message-ID: | CAG7mmoyaNxJU2xUMsOj3mLxObEt0qsXHCObT690V5MLcdtrVPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
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>
Attachment | Content-Type | Size |
---|---|---|
Wait_only_if_thread_running.patch | application/octet-stream | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2013-07-05 12:32:16 | PATCH: Debugger with Postgres Plus Advanced Server (EnterpriseDB) |
Previous Message | Ashesh Vashi | 2013-07-05 08:37:09 | PATCH: Handling too many notices from the debugging function |