| From: | "Sumita Biswas" <sbiswas(at)cisco(dot)com> |
|---|---|
| To: | "'Carl E(dot) McMillin'" <carlymac(at)earthlink(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Cc: | "'Kris Jurka'" <books(at)ejurka(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Richard Huxton'" <dev(at)archonet(dot)com> |
| Subject: | pg_dump when used with chroot |
| Date: | 2004-07-08 23:23:10 |
| Message-ID: | 039401c46542$8bc88e00$dc656540@amer.cisco.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi All,
I am facing an issue with pg_dump, please let me know if there is a
solution to this.
I have a database called 'car' on one partition , on which I have the
Postgres Server running.
When I run a script from another partition on the same machine, which
does a pg_dump, the pg_dump is unable to find the car database.
The reason here might be the pg_dump command is run as chroot and chroot
is /partB.
The car database is on /.
So the pg_dump command tries to find a car database on /partB, which
does not exist.
Is there a way by which I can run the pg_dump from a different root, and
make it backup a database on a different root?
Regards,
Sumita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wheeler | 2004-07-08 23:23:42 | ANNOUNCE: Bricolage 1.8.1 |
| Previous Message | Grant McLean | 2004-07-08 22:52:03 | Re: Slow deletion of data from tables |