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

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)

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

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.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:

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)



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Just to confirm also

I dumped the database and restored to a Suse Linux 9.3 Box

Same problem occurs (different alloc request size though)

I can forward a dump of the database if required

Cheers
Garrett

-----Original Message-----
From: pgsql-bugs-owner (AT) postgresql (DOT) org
[mailtogsql-bugs-owner (AT) postgresql (DOT) org] On Behalf Of Garrett Heaver
Sent: 04 September 2005 17:14
To: 'Alvaro Herrera'
Cc: pgsql-bugs (AT) postgresql (DOT) org
Subject: Re: [BUGS] GiST intarray Memory Allocation

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.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:

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)



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match



---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

"Garrett Heaver" <garrett.heaver (AT) researchandmarkets (DOT) com> writes:
Please (unless you've already heard from Oleg or Teodor, who are
probably more qualified to debug it than I am). Offlist of course.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match