Skip site navigation (1) Skip section navigation (2)

Re: Capturing vacuum output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rickard <David(dot)Rickard(at)GTScompanies(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org,Judith Strawser <judiths(at)GTScompanies(dot)com>,Don Walters <dwalters(at)GTScompanies(dot)com>
Subject: Re: Capturing vacuum output
Date: 2003-10-29 22:35:05
Message-ID: 23563.1067466905@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
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

In response to

pgsql-novice by date

Next:From: Mel JameroDate: 2003-10-30 07:05:44
Subject: Re: derive the sequence name of a column
Previous:From: Oliver ElphickDate: 2003-10-29 21:53:47
Subject: Re: logging messages this time

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group