Re: Capturing vacuum output

David Rickard <David(dot)Rickard(at)GTScompanies(dot)com> writes:
> all that gets captured is the backend database commands--VACUUM <dbname>
> etc; thinking that the verbose output was going to something besides
> stdout, we tried

> vacuumdb -a -f -z -v 2> ${pg_log}/vaclog.log

> and got the error message: "cannot vacuum all databases and a specific one
> at the same time";
> To what I/O stream does the verbose output get written, and how can we
> capture it?

It goes to stderr. The above command looks okay to me; perhaps you need
to get rid of the spaces between 2> and the target file. It sounds like
vacuumdb thinks it is seeing an additional command-line argument besides
the switches.

regards, tom lane