From: | Devin Whalen <devin(at)synapticvision(dot)com> |
---|---|
To: | olly(at)lfix(dot)co(dot)uk |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Sending errors from psql to error file |
Date: | 2004-08-12 15:01:21 |
Message-ID: | 1092322881.23985.38.camel@192.168.1.80 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Thu, 2004-08-12 at 10:50, Oliver Elphick wrote:
> On Thu, 2004-08-12 at 15:20, Devin Whalen wrote:
> > Hello,
> >
> > I am trying to migrate a client from one database to another. Basically
> > we designed a web application for them using Postgresql but we have made
> > many changes to the design of our application since version 1. Now they
> > want to upgrade. So basically I have to pg_dump their current data and
> > then import it into our new schema. Now, of course I realize that there
> > are going to be errors. But they have a lot and I mean a lot of data.
> > I don't want to have to sit there and watch the import go by, I want to
> > run a command and then look in a file for any errors after the import is
> > complete. I tried this command but it didn't work:
> > gunzip -c cli_postDataInserts.sql.gz | psql cli_post -U system | grep
> > "ERROR:*" > import_errors
> >
> > Any help is appreciated.
>
> 1. "didn't work" is not much help
Ok sorry. I ran the command and there were errors printed to the screen
but they did not get piped into grep and then redirected into the file
import_errors.
>
> 2. Use the --echo-queries and -f options to psql and capture all the
> output; a bare error line won't tell you much about what happened nor
> where it happened - you need to see what query was running. The -f will
> let psql report which line in the input.
>
> zcat cli_postDataInserts.sql.gz |
> psql -d cli_post -U system --echo-queries -f - >trace.file 2>&1
Just a few questions about your command. I tried it with one sql
statement that I know doesn't work and the error went into the right
file. However, I would like to know WHY it works...hope you don't mind
shedding some light on it :). Specifically, the - >trace.file 2>&1
part. I know...well actually think, that the > is redirecting the ouput to the trace.file. But what the hell is 2>&1 doing??
Also, the - ...it kinda just looks like a stray dash to me....although I know it must be doing something ;).
Will this put all output? Or just the errors.
> Oliver Elphick
Thanks for the help BTW, it is a really nice command.
--
Devin Whalen
Programmer
Synaptic Vision Inc
Phone-(416) 539-0801
Fax- (416) 539-8280
1179A King St. West
Toronto, Ontario
Suite 309 M6K 3C5
Home-(416) 653-3982
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2004-08-12 15:09:21 | Re: Sending errors from psql to error file |
Previous Message | Richard Huxton | 2004-08-12 15:00:31 | Re: Sending errors from psql to error file |