Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5E9AB4759EA for ; Wed, 21 Aug 2002 01:33:33 -0400 (EDT) Received: from joeconway.com (unknown [63.210.180.150]) by postgresql.org (Postfix) with ESMTP id C4718475978 for ; Wed, 21 Aug 2002 01:33:32 -0400 (EDT) Received: from [192.168.5.2] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 3.5.9) with ESMTP-TLS id 1291660; Tue, 20 Aug 2002 22:21:16 -0700 Message-ID: <3D6325FC.8020608@joeconway.com> Date: Tue, 20 Aug 2002 22:32:44 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Rod Taylor , PostgreSQL-development Subject: Re: Proposal: make "opaque" obsolete References: <18530.1029866880@sss.pgh.pa.us> <1029867570.99470.82.camel@jester> <19248.1029868284@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/1576 X-Sequence-Number: 27260 Tom Lane wrote: > The reason I bring this up is that if we are changing the internal > representation of arrays, we could add type OID and perhaps typmod to > the array header, thus making an array value interpretable without any > outside info. Then you could actually do something interesting with > a function taking anyarraytype. This sounds very cool. I'd vote for that. Joe