Re: BUG #13633: ERROR: invalid memory alloc request size

From: Andreas Hauser <andreas-postgresql(at)creative-memory(dot)de>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13633: ERROR: invalid memory alloc request size
Date: 2015-09-22 18:09:31
Message-ID: 201509221809.t8MI9VHI030286@sol.creative-memory.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

tgl wrote @ Tue, 22 Sep 2015 12:48:40 -0400:
> andreas-postgresql(at)creative-memory(dot)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?
>
> regards, tom lane

Yes and pg_dumpall works.
The dump is 32GB, the machine has 128GB, work_mem = 70G.

After filling the added serial, disk usage more than doubled
to 221GB. Vacuum did not change this.

I had similar problems with 9.4.4, but switched to 9.5. to be able
to fill the new serial field with a sub-select. The query using the
text id gave the same problem, but sometimes it worked (repeatedly
submitting it with pipe to pgsql would sometimes succeed and run
for about an hour).

Cheers
Andreas

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2015-09-22 19:58:16 Re: BUG #13630: initdb - libreadline.so.6 symbol BC error
Previous Message Tom Lane 2015-09-22 16:48:40 Re: BUG #13633: ERROR: invalid memory alloc request size