Thread: pgadmin III - database backup / restore
I'm investigating the use of Postgres for a future project & have installed beta 8.0 using the windows installer which includes pgadmin III. Everything works great, I can create tables etc. Connect from external applications... but, no matter what I do the Backup and Restore options on the pgadmin Tools menu remain disabled (irrespective of selected node in the tree). I can't find any mention of this feature in the online help or on mailing lists etc. Can anyone enlighten me ?? Paul ************************************************************ Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or Maritime Safety Queensland, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. ************************************************************
paul.n.shortis@mainroads.qld.gov.au wrote:
>
>
>
> I'm investigating the use of Postgres for a future project & have installed
> beta 8.0 using the windows installer which includes pgadmin III. Everything
> works great, I can create tables etc. Connect from external applications...
> but, no matter what I do the Backup and Restore options on the pgadmin
> Tools menu remain disabled (irrespective of selected node in the tree). I
> can't find any mention of this feature in the online help or on mailing
> lists etc.
>
> Can anyone enlighten me ??
Backup/restore gui is the newest feature in pgAdmin3; please use the
very latest snapshot (2004-08-15) from www.pgadmin.org. Doc has to be
written.
You have to select which object you'd like to backup. You can backup a
database, a schema or a table.
You have to select a database or table to restore. After selecting the
backup file, you can examine it for contents ("view"). If you launched
"restore database", you also can select a single object to restore from
the contents.
If backup/restore remains disabled when selecting a database, the tools
pg_dump/pg_restore are not accessible (path or directory where
pgadmin3.exe lives). pgadmin3.zip includes them.
Regards,
Andreas
On 16 Aug 2004 at 10:53, Andreas Pflug wrote: > If backup/restore remains disabled when selecting a database, the tools > pg_dump/pg_restore are not accessible (path or directory where > pgadmin3.exe lives). pgadmin3.zip includes them. Is there any way of telling pgAdmin where these live? - or do they need to be in the PATH or something? --Ray. ------------------------------------------------------------- Raymond O'Donnell http://www.galwaycathedral.org/recitals rod@iol.ie Galway Cathedral Recitals -------------------------------------------------------------
Raymond O'Donnell wrote: > On 16 Aug 2004 at 10:53, Andreas Pflug wrote: > > >>If backup/restore remains disabled when selecting a database, the tools >>pg_dump/pg_restore are not accessible (path or directory where >>pgadmin3.exe lives). pgadmin3.zip includes them. > > > Is there any way of telling pgAdmin where these live? No. Put them together with libpq.dll and zlib.dll into the same directory as pgadmin3. Regards, Andreas
Please do NOT mail directly, use the list. paul.n.shortis@mainroads.qld.gov.au wrote: > > > > Placing pg_dump & company in the pgadmin3 directory made the tools menu > option availble; however the backup procedure locks up pgadmin 3 with a > command line prompt in the messages portion of the backup dialog. I assume > that pgadmin is waiting for pg_dump to return, but pg_dump is waiting for > user input that isn't forthcoming ?? Try executing the command which is displayed on the message page on a command line, what's happening? Regards, Andreas
Sorry about that Andreas, I'm used to the Xitami list where I just reply to a message and it automatically goes to the list. When I run pg_dump with or without the -U switch to provide the db user name, I always get prompted for a password, then (providing the passsword was correct) the dump executes successfully. Since pg_dump doesn't have a switch to supply the password (it always appears to want the password interactively) I would guess that pgadmin would need to supply stdin to the spawned copy of pg_dump. As it stands pg_dump just sits waiting for a password and pgadmin becomes unresponsive - wouldn't it be better if pgadmin used events to detect pg_dump activity or ran pg_dump on another thread to avoid hanging the main evet loop of pgadmin (& hence the lock up) when this type of thing occurs ? Regards, Paul Please do NOT mail directly, use the list. paul.n.shortis@mainroads.qld.gov.au wrote: > > > > Placing pg_dump & company in the pgadmin3 directory made the tools menu > option availble; however the backup procedure locks up pgadmin 3 with a > command line prompt in the messages portion of the backup dialog. I assume > that pgadmin is waiting for pg_dump to return, but pg_dump is waiting for > user input that isn't forthcoming ?? Try executing the command which is displayed on the message page on a command line, what's happening? Regards, Andreas ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.orgso that your message can get through to the mailing list cleanly ************************************************************ Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or Maritime Safety Queensland, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. ************************************************************
paul.n.shortis@mainroads.qld.gov.au wrote: > > > > > Sorry about that Andreas, I'm used to the Xitami list where I just reply to > a message and it automatically goes to the list. > > When I run pg_dump with or without the -U switch to provide the db user > name, I always get prompted for a password, then (providing the passsword > was correct) the dump executes successfully. Oh dear, I didn't notice that. I always tested on trusted connections. > > Since pg_dump doesn't have a switch to supply the password (it always > appears to want the password interactively) I would guess that pgadmin > would need to supply stdin to the spawned copy of pg_dump. Will take me some time to fix. Regards, Andreas