| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
| Cc: | "Moreno Andreo" <moreno(dot)andreo(at)evolu-s(dot)it>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Invalid field size |
| Date: | 2017-07-04 19:09:45 |
| Message-ID: | 11529.1499195385@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
> Tom Lane wrote:
>> 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,
Oh, I'd forgotten about that.
> so I would expect COPY IN to stumble on a corrupted signature
> and abort earlier in the process, if that conversion occurred.
Right. I'm probably barking up the wrong tree, then.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-04 19:23:07 | Re: 64bit initdb failure on macOS 10.11 and 10.12 |
| Previous Message | Rainer J.H. Brandt | 2017-07-04 18:56:23 | 64bit initdb failure on macOS 10.11 and 10.12 |