Gordon Shannon writes:
> Got it. The problem was a combination of 2 mis-matched data types.
> ...
> So, my fault, and the fix is obvious. But it does seem like a less than
> ideal error message.
The binary format is sufficiently non-redundant that it's hard for the
code to know just what is wr
Tom Lane-2 wrote:
>
> Gordon Shannon writes:
>
>> ERROR: insufficient data left in message
>> CONTEXT: COPY mytable, line 1, column provider_id
>
>> Anybody seen this?
>
> No. Can you extract a self-contained test case?
>
Got it. The problem was a combination of 2 mis-matched dat
Gordon Shannon writes:
> I'm running 8.4 on Linux/Centos. I am doing a "copy (select ) to
> '/absolute/path/to/file.dat' with binary". That works fine. But when I load
> that file into a table...
> copy mytable (id, mlid, parent_mlid, author_id, date_id, time_id,
> content_type_id, provid
Hello,
I'm running 8.4 on Linux/Centos. I am doing a "copy (select ) to
'/absolute/path/to/file.dat' with binary". That works fine. But when I load
that file into a table...
copy mytable (id, mlid, parent_mlid, author_id, date_id, time_id,
content_type_id, provider_id,
is_duplica
