From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Maintenance form exection thread |
Date: | 2010-04-06 19:01:34 |
Message-ID: | p2s937d27e11004061201n3a595d86t2c6717a3ed44a544@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
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.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-04-06 19:48:20 | Re: Maintenance form exection thread |
Previous Message | Dave Page | 2010-04-06 18:13:15 | Re: Query tool execute to file prompting |