Tom Lane wrote: > > ERROR: literal carriage return found in data > > HINT: Use "\r" to represent carriage return. > > CONTEXT: COPY FROM, line 41 > > Really? 7.2 should dump data \r or \n as the backslash versions ... > and does in my tests. Can you make a reproducible test case? > > > > > It would be nice to have such occurances echo the table / row they are > > getting the error on, or maybe just the first 20 or so characters, so > > they'd be easier to identify. > > That's not a bad idea. I think it would be fairly easy now for the > CONTEXT line of the error message to include the input data line: > > CONTEXT: COPY FROM, line 41: "data here ...." > > at least up through the field where the error gets thrown, and with some > limit on the length of the data that will get echoed. If people like > that idea I'll see about making it happen.
Also, he wanted table name too. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
