| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Thom Brown <thombrown(at)gmail(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feature request: threaded processes |
| Date: | 2010-06-01 16:34:46 |
| Message-ID: | AANLkTilCgLy6rNIvYnIxdXRCj1wGx2gCoc97xDZI4SjC@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, Jun 1, 2010 at 5:32 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le 01/06/2010 16:45, Thom Brown a écrit :
>> I notice that pgAdmin often locks up while it's doing something, like
>> vacuuming or restoring a database. Would it be possible to have this
>> run in a separate thread instead of locking the whole app up?
>
> The maintenance dialog uses the same connection than the browser one in
> 1.10. It's fixed in 1.12.
>
> Restoring a database is done with pg_restore which uses its own connection.
And runs in an separate thread.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | svn | 2010-06-02 08:25:12 | SVN Commit by dpage: r8399 - trunk/pgadmin3/pgadmin/dlg |
| Previous Message | Guillaume Lelarge | 2010-06-01 16:32:36 | Re: Feature request: threaded processes |