Re: Invalid field size

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Invalid field size
Date: 2017-07-04 15:42:15
Message-ID: 6e59ffe4-5c58-a714-deab-143a67788efb@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/04/2017 08:37 AM, Moreno Andreo wrote:
> Il 04/07/2017 17:25, Tom Lane ha scritto:
>> Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> writes:
>>> Il 04/07/2017 16:51, Tom Lane ha scritto:
>>>> Pushing binary data around on Windows is always a hazardous
>>>> proposition.
>>> So what you are saying is "in the last 5 years you've been extremely
>>> lucky?" :-)
>> Yup, particularly now that you mention moving the files between machines.
>> What did you do that with exactly?
> Trying to answer your question (I hope I understood correctly, English
> is not my mother tongue)

I believe what Tom was asking is what mechanism/tools do you use to move
the 2 files below from one machine to another?

> What I do is, given a database, to COPY every table to a file, and then
> pack them up in one with a zip (except this table, that's been excluded
> from compression for its size and consequent compression time), so my
> backup is made up by 2 files, one with "normal data" and one with the
> result of COPYing this table to a file.
>
> A question that comes while I'm writing: but pg_dump with custom format
> is not using COPY with binary format?
>
> Thanks
> Moreno
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Verite 2017-07-04 15:42:41 Re: Invalid field size
Previous Message Adrian Klaver 2017-07-04 15:39:24 Re: Invalid field size