From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Theo Kramer <theo(at)flame(dot)co(dot)za> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] COPY |
Date: | 1999-08-13 14:09:26 |
Message-ID: | 4163.934553366@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Theo Kramer <theo(at)flame(dot)co(dot)za> writes:
> I've been doing some big imports using COPY. Problem I have is COPY
> aborting if a field could not be parsed. What's the feeling about
> changing the behaviour so it does not abort, yet writes the offending line
> number to the error log and continues with the next line?
I can think of situations where you'd want it either way. (For example,
in a pg_dump restore script I'd sure want big red warning flags if there
were any problems, not a piddly little message in the postmaster log...)
How about creating a SET variable that chooses either the above behavior
or the existing one?
If that seems acceptable all 'round, we can start arguing about which
way ought to be the default ;-)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-08-13 14:13:43 | Re: [HACKERS] Token length limit |
Previous Message | Marc Howard Zuckman | 1999-08-13 13:05:24 | Re: [HACKERS] COPYz |