In article <414F2471.9050104 (AT) insys-corp (DOT) com.mx>, Eduardo Vázquez
Rodríguez <evazquez (AT) insys-corp (DOT) com.mx> wrote:

Hola Eduardo

I'm using the MacOSX package, which suggests your q1 should be revised
to /usr/local/pgsql/data.

I'm still a novice to postgresql, but as I have just researched the
backup issue in the O'Reilly book, I'll have a go at answering q2.

pg_dump will do this for you; you don't have to be in the pgsql
directory, pg_dump can even be run from another server.

My best guess is to run the command from the other partition. So it
would be something like:

# pathto/usr/local/bin/pg_dump --file=youdata.sql --format=p yourdata

you have a choice of formats: c=gzip, t=tar, p=plain text

If you wanted to backup the entire filesystem, stop the server and make
a copy, something like this (compressed):

# cd /usr/local/pgsql
# /usr/local/bin/pg_ctl stop
# tar czf pgsql.bak.tar.gz data/

then you can

# mv pgsql.bak.tar.gz /path/to/where/you/want

or cp to be safe!

Well, that's my solution. I did try out various options myself on a
testdb, with no problems. So I hope I'm not misleading you.

Buena suerte

Neacal

At 02:41 PM 9/20/04, Eduardo Vázquez Rodríguez wrote:

This works for me (replace [database] with name of your database):

pg_dump -o -c [database] | gzip > /home/postgres/[database].`date
+\%Y\%m\%d`.gz

Frank


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org