Thread: [pgAdmin III] #165: Maintenance work blocks UI - use separate connection?

#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

#165: Maintenance work blocks UI - use separate connection?
----------------------+-----------------------------------------------------
 Reporter:  mha       |       Owner:          
     Type:  bug       |      Status:  assigned
 Priority:  critical  |   Milestone:          
Component:  pgadmin   |     Version:  1.10    
 Keywords:            |    Platform:  all     
----------------------+-----------------------------------------------------
Changes (by mha):

  * owner:  dpage =>
  * status:  new => assigned


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

#165: Maintenance work blocks UI - use separate connection?
----------------------+-----------------------------------------------------
 Reporter:  mha       |       Owner:  gleu    
     Type:  bug       |      Status:  assigned
 Priority:  critical  |   Milestone:          
Component:  pgadmin   |     Version:  1.10    
 Keywords:            |    Platform:  all     
----------------------+-----------------------------------------------------
Changes (by gleu):

  * owner:  => gleu


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

#165: Maintenance work blocks UI - use separate connection?
-------------------------+--------------------------------------------------
 Reporter:  mha          |       Owner:  gleu    
     Type:  bug          |      Status:  assigned
 Priority:  critical     |   Milestone:  1.12    
Component:  pgadmin      |     Version:  1.10    
 Keywords:  maintenance  |    Platform:  all     
-------------------------+--------------------------------------------------
Changes (by gleu):

  * keywords:  => maintenance
  * milestone:  => 1.12


Comment:

 Done in r8266.

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

#165: Maintenance work blocks UI - use separate connection?
-----------------------+----------------------------------------------------
  Reporter:  mha       |       Owner:  gleu       
      Type:  bug       |      Status:  closed     
  Priority:  critical  |   Milestone:  1.12       
 Component:  pgadmin   |     Version:  1.10       
Resolution:  fixed     |    Keywords:  maintenance
  Platform:  all       |  
-----------------------+----------------------------------------------------
Changes (by gleu):

  * status:  assigned => closed
  * resolution:  => fixed


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