| From: | Raymond O'Donnell <rod(at)iol(dot)ie> |
|---|---|
| To: | Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>, Rob Richardson <RDRichardson(at)rad-con(dot)com>, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Why do backups take so long? |
| Date: | 2015-03-07 12:32:40 |
| Message-ID: | 54FAEFE8.6020304@iol.ie |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On 07/03/2015 00:15, Jan-Peter Seifert wrote:
> Am 06.03.2015 um 19:33 schrieb Raymond O'Donnell:
>
>> pgAdmin just uses pg_dump [1] to do the actual backup, so it would be
>> interesting to run pg_dump directly at the command line to see if the
>> same behaviour manifests itself.
>
> There's nothing interesting about that, because this behaviour is really
> old news:
> http://www.postgresql.org/message-id/20110103123027.118630@gmx.net
>
> Running pg_dump from command line directly works without problems.
>
> Makes me wonder whether the Windows version of pgAdmin is still being
> tested on xp only.
It works fine for me - Windows 7 Home on my laptop, 64-bit, with pgAdmin
III 1.20.0. The interface flashes as described in the message linked
above - presumably as pgAdmin spawns and interacts with a new process
for pg_dump - but the entire operation takes no more than 5s with a tiny
database.
Ray.
--
Raymond O'Donnell :: Galway :: Ireland
rod(at)iol(dot)ie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hushthatbush | 2015-03-07 13:31:36 | Can somebody UNSUBSCRIBE me from this group? |
| Previous Message | Jan-Peter Seifert | 2015-03-07 00:15:40 | Re: Why do backups take so long? |