pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Casey Duncan <casey@pandora.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Paul B. Anderson <paul.a@pnlassociates.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-general@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure array limits)
Date: Fri, 29 Sep 2006 09:35:25 -0700
Message-ID: <595CA7DC-7EC2-47B6-A894-DCD0ED3825F3@pandora.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>

On Sep 29, 2006, at 9:14 AM, 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?

At first blush, this strikes me as a bit too magical/implicit. Are  
there other languages where sequences behave similarly? The best  
analogy that comes to mind is sparse files, but in that case there is  
an implicit contract that the intervening empty regions do not  
actually occupy physical space, doesn't sound like that's true here.

I think the result of this change would be more difficult debugging  
of off-by-one errors and their ilk, rather than actually being a real  
benefit.

OTOH, perhaps there is a real use-case I am missing here. I don't see  
the rest of this thread on GENERAL and I couldn't find it searching  
the archives, where did it come from?

-Casey




view thread (7+ messages)  latest in thread

Message-ID: <595CA7DC-7EC2-47B6-A894-DCD0ED3825F3@pandora.com>
Permalink:  ../595CA7DC-7EC2-47B6-A894-DCD0ED3825F3@pandora.com/
Also on:    postgresql.org/message-id/595CA7DC-7EC2-47B6-A894-DCD0ED3825F3@pandora.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: casey@pandora.com, tgl@sss.pgh.pa.us, paul.a@pnlassociates.com, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org
  Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure array limits)
  In-Reply-To: <595CA7DC-7EC2-47B6-A894-DCD0ED3825F3@pandora.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> <595CA7DC-7EC2-47B6-A894-DCD0ED3825F3@pandora.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