From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Jan Wieck <jan(at)wi3ck(dot)info>, Stefan Blanke <stefan(dot)blanke(at)framestore(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: ERROR: invalid memory alloc request size 1073741824 |
Date: | 2018-01-30 22:00:29 |
Message-ID: | 28d517a9-bf36-1a79-c2e7-6356dcd31064@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/30/2018 10:43 PM, Jan Wieck wrote:
>
>
> On Tue, Jan 30, 2018 at 12:35 PM, Stefan Blanke
> <stefan(dot)blanke(at)framestore(dot)com <mailto:stefan(dot)blanke(at)framestore(dot)com>> wrote:
>
> Hello,
>
> We've tripped over an error when doing a "COPY.. TO STDOUT WITH
> BINARY" query.
>
> "ERROR: invalid memory alloc request size 1073741824"
> (exactly 1GB)
>
>
> I have my money on a corrupted TOAST entry. Is this happening on
> trustworthy hardware or beige box with no ECC or RAID?
>
I'll bet you it's not that. It's quite unlikely that would fail with
exactly 1GB request size. It seems much more like a buffer that we keep
to be power of 2. The question is which one.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2018-01-30 22:03:18 | Re: Alter view with dependence without drop view! |
Previous Message | Ken Tanzer | 2018-01-30 21:50:58 | Re: Alter view with dependence without drop view! |