From: | Chris Pesko <cpesko(at)organic(dot)com> |
---|---|
To: | missive(at)hotmail(dot)com, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: complete output to file?? |
Date: | 2001-10-04 18:37:16 |
Message-ID: | 4.3.2.7.2.20011004113541.01dc6d10@mailhost.organic.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thank you very much. I will try your suggestions. I'm new to PostgreSQL
and I'm very happy with the quick responses I'm getting from the email
subscription. It's a great help. When I get better I will return the
favors to others in need.
At 12:09 AM 10/4/01 +0000, Lee Harr wrote:
> > I use \o [file] to get output to a file but it only records the
> > command. For example:
> >
> > \o vac.out
> > vacuum verbose analyze;
> >
> > I end up with one row "VACUUM" in vac.out. I want the entire output
> that I
> > see on the screen to go to a file. How is this done?
> >
>
>
>I am not sure how to do this entirely within psql, but you can always
>use the vacuumdb command or the -c flag to psql...
>
>
>vacuumdb --verbose --analyze -d databasename >& output.txt
>psql -c 'vacuum verbose analyze' databasename >& output.txt
>
>
>Note that you must redirect both stdout and stderr to your file
>in order to see everything. That seems to be why \o is not catching
>the output that you want.
>
>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Buchmann | 2001-10-04 18:57:03 | Re: help with an install problem |
Previous Message | Chris Pesko | 2001-10-04 17:11:10 | Re: Storage management????? |