Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 7C1099FB2F1 for ; Thu, 28 Sep 2006 21:50:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 22776-10 for ; Fri, 29 Sep 2006 00:50:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 472089FB2D1 for ; Thu, 28 Sep 2006 21:50:40 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 0FC3856427; Thu, 28 Sep 2006 19:50:39 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 28 Sep 2006 19:50:38 -0500 Date: Thu, 28 Sep 2006 19:50:38 -0500 From: "Jim C. Nasby" To: "Paul B. Anderson" Cc: pgsql-admin@postgresql.org Subject: Re: Addendum on stored procedure array limits Message-ID: <20060929005038.GN34238@nasby.net> References: <451C48F0.30507@pnlassociates.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <451C48F0.30507@pnlassociates.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060929:paul.a@pnlassociates.com::0yD3yf3pZ79HP+Mh:0000000000000 0000000000000000000000002NoZ X-Hashcash: 1:20:060929:pgsql-admin@postgresql.org::0EYrFH8tZMDqGQFl:00000000000 0000000000000000000000001r4L X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/354 X-Sequence-Number: 23268 On Thu, Sep 28, 2006 at 06:13:04PM -0400, Paul B. Anderson wrote: > I'm running RHEL 3.0 and postgreSQL 8.1.4, compiled from source. Have you tried enforcing that there's no NULLs in the arrays? That code is pretty new (in fact, I thought it was only in 8.2...), so it's possible that therein lies the bug. I'd also look into the size of the varchars... if they're big enough you could be hitting a memory limit somewhere. In any case, the error message could certainly use improving... :) -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)