From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | "Keith C(dot) Perry" <netadmin(at)vcsn(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Restore functionality in 1.2RC2 and [possibile] |
Date: | 2004-12-03 11:33:42 |
Message-ID: | 41B04F16.3080707@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Keith C. Perry wrote:
> I might have missed this in a previous discussion but is the "restore" function
> working as of RC2 or is it not complete. The reason I ask is because one of the
> things I think would be useful (but maybe not easy to implement) is being about
> to have the copy command work files on the same node as pgadmin instead of the
> database server's filesystem. I would really like to upload my datasets without
> having to ftp the file to the server first. The backup/restore functionality
> provide a bit of a help in that it work with the filesystem you are running the
> client from.
>
> Backup (table dumping) seems to work but when I tried to restore, the OK button
> stays greyed out.
If the button is greyed out, the file selected isn't a valid file for
pgAdmin. Use COMPRESSED or TAR format for backup, PLAIN isn't readable
for pgAdmin.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-12-03 11:35:11 | Re: New feature request |
Previous Message | Andreas Pflug | 2004-12-03 11:30:35 | Re: pgadmin3 doesn't start on suse 9.2 |