Re: GiST intarray Memory Allocation

From: "Garrett Heaver" <garrett(dot)heaver(at)researchandmarkets(dot)com>
To: "'Alvaro Herrera'" <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: GiST intarray Memory Allocation
Date: 2005-09-04 16:14:04
Message-ID: MAILjEmHkYv1zMAf86300006a04@mail.researchandmarkets.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Performed full table select - worked perfectly

I can give you a dump of the table if that will help

Thanks
Garrett

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre(at)alvh(dot)no-ip(dot)org]
Sent: 04 September 2005 17:09
To: Garrett Heaver
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] GiST intarray Memory Allocation

On Sun, Sep 04, 2005 at 04:49:27PM +0100, Garrett Heaver wrote:

> I have a table with circa 5.5Million rows and an int4[] column containing
> about 28 elements each.
>
> When I try to put a CREATE INDEX name ON table USING gist(column);
> I get the following :
>
> ERROR: invalid memory alloc request size 2825271912

Hmm. Have you tried a plain
SELECT * FROM table?

It sounds like your table may be corrupt.

Another alternative is that the opclass functions are buggy. If the
table is not corrupt, you could try giving us complete working
instructions to try to reproduce the bug.

--
Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end." (2nd Commandment for C programmers)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Garrett Heaver 2005-09-04 19:24:10 Re: GiST intarray Memory Allocation
Previous Message Alvaro Herrera 2005-09-04 16:08:57 Re: GiST intarray Memory Allocation