RE: Trouble Upgrading Postgres

From: <bend(at)linux4ms(dot)net>
To: "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: RE: Trouble Upgrading Postgres
Date: 2018-11-06 18:43:53
Message-ID: 20181106114353.2b8d81ae03f6297615f26284cd7372ff.e8893fa0fa.wbe@email18.godaddy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

</div>
</blockquote></span></body></html>

Attachment Content-Type Size
unknown_filename text/html 2.5 KB

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2018-11-06 18:52:55 Re: backend crash on DELETE, reproducible locally
Previous Message Tom Lane 2018-11-06 18:41:21 Re: why select count(*) consumes wal logs