Re: [uug] postgres copy file to table

[Lars E. Olson]

(Did anyone ever reply to this?)  It may not be a buffer overflow, it 
may be issues with end-of-line characters.  I know that a lot of 
programs (Windows and Unix both) kind of expect one type of EOL and 
behave really funny when they get a different type.  The symptom in Unix 
programs is that it prints out the rest of the line starting with the 
first column on the same line (i.e. carriage-return without advancing 
the line-feed) which looks something like your error message.

Some annoying artifact of the old line-printer-based workstations in 
days of yore.

/me continues trying to catch up on backed-up e-mails

				Lars

Casey T. Deccio wrote:

Okay, I've spent a lot of time on this bug, and I can't figure it out. 
Hopefully someone can help me get it.  The following are the files I'm
using:

filltables.sql:
create table applicant_tmp (
    ssn char(10),
    inq int,
    act int);
copy applicant_tmp from 'table.txt' with delimiter '\t' null '';
table.txt:
012345678   0   0
I use the command `psql -f filltables.sql dbname`, and it gives me the
following error:
CREATE TABLE
": can't parse "les.sql:7: ERROR:  copy: line 1, pg_atoi: error in "0
It makes me think that I'm overflowing a buffer somewhere because the
error is weird and incomplete.  But I honestly can't see what is going
on.  Any ideas are welcome.  Thanks,
Casey

------------------------------------------------------------------------

____________________
BYU Unix Users Group 
http://uug.byu.edu/ 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list


____________________
BYU Unix Users Group 
http://uug.byu.edu/ 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list