Re: BUG #13633: ERROR: invalid memory alloc request size - Mailing list pgsql-bugs

From Andreas Hauser
Subject Re: BUG #13633: ERROR: invalid memory alloc request size
Date
Msg-id 201509230804.t8N84ZvD000582@sol.creative-memory.de
Whole thread Raw
In response to Re: BUG #13633: ERROR: invalid memory alloc request size  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: BUG #13633: ERROR: invalid memory alloc request size  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
david.rowley wrote @ Wed, 23 Sep 2015 10:57:25 +1200:
>
> On 23 September 2015 at 04:48, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> > andreas-postgresql@creative-memory.de writes:
> > > SELECT G.MarkerID,G.Allel1,G.Allel2, count (G.TierLIDint) as nH
> > >   FROM GenotypHD as G, TiereInSets as TS, Marker as M
> > >     WHERE TS.TierSetID='HD.09.15' and TS.TierLIDint=G.TierLIDint and
> > > M.Version='3' and M.MarkerID=G.MarkerID and G.Allel1<>G.Allel2
> > >     GROUP BY G.MarkerID,G.Allel1,G.Allel2;
> >
> > > ERROR:  invalid memory alloc request size 1073741824
> >
> > FWIW, I could not reproduce this on the basis of the supplied information,
> > ie just creating the tables and running this query does not do anything
> > surprising.  It looks like possibly a corrupt-data issue --- can you do
> > "select * from" each table without problems?
> >
> >
> This seems related to this
> http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010F6F3F@BPXM15GP.gisp.nec.co.jp
>
> work_mem, I believe, must be higher than 1GB to trigger this.
>

I can confirm that it works when work_mem is reduced to 1GB.

Cheers and thanks
Andreas

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #13601: bit as quoted column in output
Next
From: Tom Lane
Date:
Subject: Re: BUG #13633: ERROR: invalid memory alloc request size