From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
cc: "Alvaro Herrera" <alvherre@2ndquadrant.com>,
        "Robert Haas" <robertmhaas@gmail.com>,
        "Jim Nasby" <Jim.Nasby@bluetreble.com>,
        "Ronan Dunklau" <ronan.dunklau@dalibo.com>,
        "pgsql-hackers" <pgsql-hackers@postgresql.org>
Subject: Re: pg_dump / copy bugs with "big lines" ?
In-reply-to: <4023faba-72cc-4949-b11c-8c67a0ecf407@mm>
References: <4023faba-72cc-4949-b11c-8c67a0ecf407@mm>
Comments: In-reply-to "Daniel Verite" <daniel@manitou-mail.org>
	message dated "Tue, 01 Mar 2016 17:43:00 +0100"
Date: Tue, 01 Mar 2016 11:50:36 -0500
Message-ID: <14620.1456851036@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

"Daniel Verite" <daniel@manitou-mail.org> writes:
> 	Alvaro Herrera wrote:
>> If others can try this patch to ensure it enables pg_dump to work on
>> their databases, it would be great.

> It doesn't seem to help if one field exceeds 1Gb, for instance when
> inflated by a bin->hex translation.

It's not going to be possible to fix that without enormously invasive
changes (affecting individual datatype I/O functions, for example).
And in general, fields approaching that size are going to give you
problems in all kinds of ways, not only COPY.

I think we should be satisfied if we can make COPY deal with the sum
of a line's fields exceeding 1GB.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers