From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Maintenance form exection thread |
Date: | 2010-04-06 20:33:34 |
Message-ID: | 4BBB9A9E.8040702@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Le 06/04/2010 21:48, Magnus Hagander a écrit :
> On Tue, Apr 6, 2010 at 21:01, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> On Tue, Apr 6, 2010 at 6:11 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> Hi!
>>>
>>> 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?
>>
>> Yeah, that would seem like a sensible idea. At first thought I guessed
>> it was an issue like this
>> http://svn.pgadmin.org/cgi-bin/viewcvs.cgi?rev=6458&view=rev, but on
>> reflection I think your much more simple explanation is the likely
>> cause.
>
> I don' t have time to look into it right onw. Do you, or should I just
> add a ticket for it for "eventual fixing"?
>
Add the ticket, I will take care of it this week if no one does.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2010-04-06 20:36:38 | SVN Commit by guillaume: r8257 - in trunk/pgadmin3: . pgadmin/dlg pgadmin/ui |
Previous Message | Magnus Hagander | 2010-04-06 19:48:20 | Re: Maintenance form exection thread |