Re: Trouble Upgrading Postgres

The column is a bytea.

I'm working out a way to limit the size on the front end.

Chuck

On Tue, Nov 6, 2018 at 1:44 PM <bend(at)linux4ms(dot)net> wrote:

> As someone pointed out, there is a limit with bytea (Blob's).
> To test if it is bytea, use a COPY with a select statement :
>
> COPY ( select A, B,C ,D ...etc FROM table ) TO 'outfile' ;
> Leaveing out the bytea column.
> If this works, then then one of the bytea columns is way to big.
>
> Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS,
> 39212
> "Never attribute to malice, that which can be adequately explained by
> stupidity"
> - Hanlon's Razor
>
>
> -------- Original Message --------
> Subject: Re: Trouble Upgrading Postgres
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date: Tue, November 06, 2018 11:53 am
> To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
> Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, Charles Martin
> <ssappeals(at)gmail(dot)com>, pgsql-general
> <pgsql-general(at)postgresql(dot)org>
>
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> > On 11/6/18 8:27 AM, Daniel Verite wrote:
> >> Adrian Klaver wrote:
> >>> To me that looks like a bug, putting data into a record you cannot get
> out.
>
> >> Strictly speaking, it could probably get out with COPY in binary format,
> >> but pg_dump doesn't use that.
>
> Another possibility, seeing that the problematic data is bytea, is that
> it might depend on whether you use hex or escape bytea_output format.
> Hex format is reliably twice the size of the stored data, but escape
> format could be anywhere from the same size as the stored data to four
> times the size, depending on the contents. pg_dump is agnostic about this
> and will just dump using the prevailing bytea_output setting, so you might
> be able to get it to work by changing that setting.
>
> regards, tom lane
>
>