Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA16652; Tue, 26 May 92 08:37:12 -0700
Message-Id: <9205261537.AA16652@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: access to user defined arrays
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Thu, 21 May 92 12:35:28 PDT."
             <9205211935.AA00814@postgres.Berkeley.EDU> 
Date: Tue, 26 May 92 08:36:56 PDT

you write:

> I can't get access to array elements other than the 0th and 1st.  Have
> I missed something fundamental or does it simply not work as it
> should?
> 
> define type foo ( input = array_in, output = array_out,
> 	internallength = 0, element = text )
> 
> create bar ( textarray = foo ) 
> 
> append bar ( textarray = "{"one","two","three","four"}")
> 
> retrieve ( bar.textarray[1] )
> ---------------
> | textarray   |
> ---------------
> | one         |
> ---------------
> 
> retrieve ( bar.textarray[2] )
> Query sent to backend is "retrieve ( bar.textarray[2] ) "
> 
> This query never returns, and often kills the postmaster.  We're
> runing Ultrix 4.2 on DECstation with Postgres 3.1.

This is a known bug in 3.1.  Arrays of variable length types, as well as
arrays of types larger than sizeof(char *) are broken.  I have been lax
in keeping the bug list up to date.  It has been repaired and the fix will
be out with version 4.

Jeff Meredith
mer@postgres.berkeley.edu