| From: | Mike Beller <beller(at)tradeworx(dot)com> |
|---|---|
| To: | Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com> |
| Cc: | Thomas Reinke <reinke(at)e-softinc(dot)com>, Jose Soares <jose(at)sferacarta(dot)com>, pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] copy command -- foiled by pg_atoi |
| Date: | 1999-12-22 14:55:56 |
| Message-ID: | 3860E67C.68F4E9E4@tradeworx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Folks--
Thanks for the ideas. But bisection just seemed too cumbersome.
In the end I decided to write a data filter in perl which checks
all the data for valid types before putting it into the DB!
Mike
Ed Loehr wrote:
>
> I have found that judicious placement of a few queries (selects, intentional
> errors, etc.) within a long sequence of inserts will help segment them for
> identification of offending lines. Hokie, but it helps me.
...
> Thomas Reinke wrote:
>
> > I've run into this a few times as well. My strategy to "hunt" down
> > the offending line has been to do a "bisection" algorithm.
> >
> > Jose Soares wrote:
> > >
> > > This is also my problem. I'm getting '@!?àù§èé+*_|!&/%§¸' to load a
> > > table with more than 23,000 rows
> > > because I don't know in which line I have to look for the the error.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | soundar rajan | 1999-12-22 15:17:54 | Trigger |
| Previous Message | Kimi | 1999-12-22 13:49:30 | Postgres performance problems. |