[pgAdmin III] #165: Maintenance work blocks UI - use separate connection? - Mailing list pgadmin-hackers

#165: Maintenance work blocks UI - use separate connection?
----------------------+-----------------------------------------------------
 Reporter:  mha       |       Owner:  dpage
     Type:  bug       |      Status:  new  
 Priority:  critical  |   Milestone:       
Component:  pgadmin   |     Version:  1.10 
 Keywords:            |    Platform:  all  
----------------------+-----------------------------------------------------
 Am I reading things right that we actually execute things from the
 maintenance dialog (like VACUUM) on a separate thread, to keep the UI
 responsive? Yet, it keeps hanging when we do that. My guess is that
 we're "using up" the connection we have, and as soon as somebody else
 needs access to the connection to do things like refresh tree
 information, we hang and wait. Or am I reading this wrong?

 If we are, should we perhaps consider firing off these jobs on a
 separate connection?

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/165>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

pgadmin-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: Missing non-login roles in properties dialog
Next
From: Dave Page
Date:
Subject: Fwd: frmMain with a wxAuiNotebook ?