Hello, the problem might be caused by the way Windows 7 64bit handles 32bit applications and/or communication between 64bit and 32bit applications. At home I use Windows 7 Ultimate 32 Bit and at work Windows 7 Enterprise 64bit. I'll have to check with the same database I dumped at work at home again, but it seems that there are no issues with Windows 7 32bit. There was no problem executing the commands generated by pgAdmin from within a DOS-Window for both versions of pg_dump in Windows 7 64bit - after quoting the path because of the spaces within. The culprit might be conhost.exe. It seems that it does a CreateFileMapping for the 9.0 version of pg_dump - even after renaming the exe. In fact pg_dump really seems to be started several times because there are different PIDs in the logs of 'Process Monitor' although I had started pg_dump just once via pgAdmin.
Hope this helps. Thank you very much, Peter -------- Original-Nachricht -------- > Datum: Wed, 16 Feb 2011 23:42:52 +0100 > Von: Guillaume Lelarge <guilla...@lelarge.info> > An: rleonanaya <roge...@blocknetworks.com.mx> > CC: pgadmin-support@postgresql.org > Betreff: Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions > Le 16/02/2011 19:41, rleonanaya a écrit : > > > > > > Guillaume Lelarge-3 wrote: > >> > >> Le 12/01/2011 18:23, jan-peter.seif...@gmx.de a écrit : > >>> Hello, > >>> > >>> -------- Original-Nachricht -------- > >>>> Datum: Tue, 11 Jan 2011 23:52:11 +0100 > >>>> Von: Guillaume Lelarge <guilla...@lelarge.info> > >>>> An: Jan-Peter Seifert <jan-peter.seif...@gmx.de> > >>>> CC: pgadmin-support@postgresql.org > >>>> Betreff: Re: [pgadmin-support] 1.12.1 - cannot dump from older server > >>>> versions > >>> > >>> I've compared the calls made by both versions of pgAdmin: > >>> > >>> 1.10.5 > >>> C:\Program Files (x86)\PostgreSQL\8.4\bin\pg_dump.exe --host localhost > >>> --port 5432 --username postgres --format custom --blobs --verbose > --file > >>> "D:\db.backup" db > >>> > >>> > >>> 1.12.2: > >>> C:\Program Files (x86)\PostgreSQL\8.4\bin\pg_dump.exe --host localhost > >>> --port 5432 --username "postgres" --format custom --blobs --verbose > >>> --file "D:\db.backup" db > >>> > >>> There's just a slight difference in that the username gets quoted by > >>> 1.12.2 > >>> > >> Yeah, that's a bug of 1.12.2, but I'm quite sure it doesn't explain the > >> time difference. Bug fixed BTW. > >> -- > >> Guillaume > >> > > > > I'm having the same behavior of Peter... > > > > My environment is: > > - PostgreSQL 9.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (Debian > > 4.3.2-1.1) 4.3.2, 32-bit > > - PgAdmin III v.1.12.2 on Win 7 64 bits > > - A 152 MB Database in UTF8 encoding > > - use backup of pgAdmin with defaults (any changes made) > > > > > > What I can see in the task manager of Win 7 is that the command pg_dump > runs > > by some seconds and then it closes, then another time it runs by some > > seconds and then it closes... I think this is what makes the refreshing > look > > of all the desktop and the slow pg_dump process. > > > > The only thing that I can assume is that the pg_dump is being made table > by > > table instead of the entire database or something like that, cause, this > > started after in the PgAdmin has delivered the "object" selector > > functionality in the backup wizard. > > > > pgAdmin launches pg_dump only once even when you ask it to dump part of > the database, table by table. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
