From: Paul B. Anderson <paul.a@pnlassociates.com>
To: pgsql-admin@postgresql.org
To: pgsql-general@postgresql.org
To: pgsql-hackers@postgresql.org
Subject: Re: Array assignment behavior (was Re: Stored procedure array
Date: Fri, 29 Sep 2006 13:08:15 -0400
Message-ID: <451D52FF.5000602@pnlassociates.com> (raw)
In-Reply-To: <16926.1159546451@sss.pgh.pa.us>
References: <451C48AB.6090508@pnlassociates.com>
<9461.1159502232@sss.pgh.pa.us>
<451D34FD.3050709@pnlassociates.com>
<451D37C8.8060502@pnlassociates.com>
<16926.1159546451@sss.pgh.pa.us>
It seems that the suggestion to fill intermediate positions with NULLs
would be preferable to the current behavior.
I know of no requirement to populate arrays in sequence in any other
language so I think other programmers would be surprised too by the
current behavior.
Paul
Tom Lane wrote:
> [ expanding this thread, as it now needs wider discussion ]
>
> "Paul B. Anderson" <paul.a@pnlassociates.com> writes:
>
>> 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?
>>
>
> Well, it's a documented behavior: section 8.10.4 saith
>
> A stored array value can be enlarged by assigning to an element
> adjacent to those already present, or by assigning to a slice
> that is adjacent to or overlaps the data already present.
>
> Up to 8.2 we didn't have a lot of choice about this, because without any
> ability to have nulls embedded in arrays, there wasn't any sane thing to
> do with the intermediate positions if you assigned to an element not
> adjacent to the existing range. As of 8.2 we could allow assignment to
> arbitrary positions by filling the intermediate positions with nulls.
> The code hasn't actually been changed to allow that, but it's something
> we could consider doing now.
>
> Comments?
>
> 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
>
> .
>
>
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, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org
Subject: Re: Array assignment behavior (was Re: Stored procedure array
In-Reply-To: <451D52FF.5000602@pnlassociates.com>
References: <451C48AB.6090508@pnlassociates.com> <9461.1159502232@sss.pgh.pa.us> <451D34FD.3050709@pnlassociates.com> <451D37C8.8060502@pnlassociates.com> <16926.1159546451@sss.pgh.pa.us> <451D52FF.5000602@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