Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id DD79D9FB2F1 for ; Thu, 28 Sep 2006 22:08:30 -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 44572-09 for ; Fri, 29 Sep 2006 01:08:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail733.megamailservers.com (mail733.megamailservers.com [69.49.98.43]) by postgresql.org (Postfix) with ESMTP id 4271C9FB2D1 for ; Thu, 28 Sep 2006 22:08:27 -0300 (ADT) X-Authenticated-User: paul.a.pnlassociates.com Received: from [69.3.2.106] (h-69-3-2-106.mclnva23.covad.net [69.3.2.106]) (authenticated bits=0) by mail733.megamailservers.com (8.13.6.20060614/8.13.1) with ESMTP id k8T18KDS010247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 28 Sep 2006 21:08:25 -0400 Message-ID: <451C7203.7000604@pnlassociates.com> Date: Thu, 28 Sep 2006 21:08:19 -0400 From: "Paul B. Anderson" User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Addendum on stored procedure array limits References: <451C48F0.30507@pnlassociates.com> <20060929005038.GN34238@nasby.net> In-Reply-To: <20060929005038.GN34238@nasby.net> Content-Type: multipart/alternative; boundary="------------000906060400030100090903" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.375 tagged_above=0 required=5 tests=HTML_30_40, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200609/355 X-Sequence-Number: 23269 This is a multi-part message in MIME format. --------------000906060400030100090903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit There are definitely nulls in there, and in the fields where the error is signaled. I missed in my reading that they are not allowed. Thanks. Paul Jim C. Nasby wrote: > 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... :) > --------------000906060400030100090903 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit There are definitely nulls in there, and in the fields where the error is signaled.  I missed in my reading that they are not allowed.

Thanks.

Paul


Jim C. Nasby wrote:
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... :)
  
--------------000906060400030100090903--