pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Paul B. Anderson <paul.a@pnlassociates.com>
To: pgsql-admin@postgresql.org
Subject: Re: Stored procedure array limits
Date: Fri, 29 Sep 2006 11:12:08 -0400
Message-ID: <451D37C8.8060502@pnlassociates.com> (raw)
In-Reply-To: <451D34FD.3050709@pnlassociates.com>
References: <451C48AB.6090508@pnlassociates.com>
	<9461.1159502232@sss.pgh.pa.us>
	<451D34FD.3050709@pnlassociates.com>

Actually, I was not filling all of the arrays in sequential order.  I 
added code to initialize them in order and the function seems to be 
working now.  Is that a known problem? 

Paul


Paul B. Anderson wrote:
> I've checked my code and it does not seem to run past any limits.  I 
> am filling the arrays in sequential order, extending each one in 
> parallel with the others.
>
> The null problem fixed the code for some cases but I'm still having 
> problems in general and with the same error message but reported in 
> another place.
>
> Paul
>
>
> Tom Lane wrote:
>> "Paul B. Anderson" <paul.a@pnlassociates.com> writes:
>>   
>>> I have a large stored procedure with 16 arrays, mostly varchar, each 
>>> with dimension 3000.  The procedure works fine on a small number of rows 
>>> used from these arrays but gets the following error for large rowsets:
>>>     
>>
>>   
>>>   ERROR:  invalid array subscripts
>>>     
>>
>> Right offhand I only see that error being thrown for out-of-range array
>> subscripts.  Are you maybe trying to fill the arrays in nonsequential
>> order?
>>
>>   
>>> If I comment out two particular arrays (that can have null values), it 
>>> also runs OK.
>>>     
>>
>> As already noted, we don't support nulls in arrays before 8.2, but
>> I'm not exactly sure how that omission leads to this error message.
>>
>> 			regards, tom lane
>>
>> .
>>
>>   

view thread (4+ messages)

Message-ID: <451D37C8.8060502@pnlassociates.com>
Permalink:  ../451D37C8.8060502@pnlassociates.com/
Also on:    postgresql.org/message-id/451D37C8.8060502@pnlassociates.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: paul.a@pnlassociates.com
  Subject: Re: Stored procedure array limits
  In-Reply-To: <451D37C8.8060502@pnlassociates.com>
  References: <451C48AB.6090508@pnlassociates.com> <9461.1159502232@sss.pgh.pa.us> <451D34FD.3050709@pnlassociates.com> <451D37C8.8060502@pnlassociates.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox