John,
Thanks for mentioning that fix :) I'm sure one could run sed or
something similar to remove that line at the top of the file after the
backup has completed (I shall have to try that sometime).
Just a note about the filesystem level backups. In my experience they
are about twice the size of the dumped data after being tar'd/gzip'd,
which isn't that big of a deal these days but something to be aware of
when allocating backup space (or writing to removable media such as CD's,
zips, tapes, whatever).
The other is just a note from the development docs for 7.1 which can be
read here
http://www.postgresql.org/devel-corner/docs/admin/backup-file.html so I
won't repeat it myself.
Tim Frank
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 21/03/01, 9:15:27 AM, John Madden <weez@freelists.org> wrote regarding
Re: [GENERAL] Really Dumb Question...(Dumping db):
> > If you have password authentication on for the other server as well try
> > this command instead,
> >
> > psql -e worldwide -f worldwide.pgdump
> >
> > where the -f switch tells psql to execute commands contained in a file.
> > I just fought with that one today for a bit until I remembered that
> > switch. You should then get a password prompt to enter your password.
> Oh, and remember to "fix" the dump file -- it'll contain the username and
> password prompts (remember that they were sent to stdout...)
> You might consider doing filesystem backups instead of the dump stuff --
> it's a great deal easier.
> John
> --
> # John Madden weez@freelists.org ICQ: 2EB9EA
> # FreeLists, Free mailing lists for all: http://www.freelists.org
> # UNIX Systems Engineer, Ivy Tech State College: http://www.ivy.tec.in.us
> # Linux, Apache, Perl and C: All the best things in life are free!
