Re: Invalid field size

From: Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Invalid field size
Date: 2017-07-05 08:05:05
Message-ID: cba790b5-b4c9-3fef-7b04-ab724fd6f908@evolu-s.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Il 04/07/2017 20:51, Daniel Verite ha scritto:
> Tom Lane wrote:
>
>> Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> writes:
>>> So the hint is to abandon manual COPY and let pg_dump do the hard work?
>> If it is a newline-conversion problem, compressed pg_dump archives would
>> be just as subject to corruption as your binary COPY file is.
> It's mentioned in [1] that the signature at the beginning of these files
> embed a CRLF to detect this newline-conversion problem early on,
> so I would expect COPY IN to stumble on a corrupted signature
> and abort earlier in the process, if that conversion occurred.
> Instead the report says it fails after a number of tuples:
Given what you said, can I assume it's a file transfer or an
hardware-driven (pendrive) problem?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message PT 2017-07-05 11:00:14 Re: Strange case of database bloat
Previous Message Jason Dusek 2017-07-05 07:23:46 Re: Imperative Query Languages