| From: | dev(at)archonet(dot)com |
|---|---|
| To: | Frank Nijenhuis <fnijen(at)bos(dot)nl> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: remote dumping of databases |
| Date: | 2001-03-06 11:56:03 |
| Message-ID: | 20010306.11560300@client.archonet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3/6/01, 8:55:05 AM, Frank Nijenhuis <fnijen(at)bos(dot)nl> wrote regarding
[GENERAL] remote dumping of databases:
[snip]
> Now I want them to be able to dump their own database. And when I use the
> command without piping the result to a file everything works.
> (pg_dump -h <remote pgsqlserver) -u <dbname>.
> You get the user prompt and password prompt..How ever..how do you get the
> content of the dump to a file??? Every pipe action will result in endless
> waiting, pg_dumps waits for the username/password.......
> Is there an solution of do I overlook something here???
You could look at wrapping pg_dump in something like "expect" or "chat"
which are designed to deal with interactive programs. You might find
useful examples relating to changing passwords since passwd has a similar
problem.
- Richard Huxton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dev | 2001-03-06 11:58:00 | Re: List of all system tables. |
| Previous Message | Renaud Tthonnart | 2001-03-06 09:28:40 | Re: libpq++ : Disconnect a DB |