Re: [HACKERS] problem with arrays - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] problem with arrays
Date
Msg-id 36942014.4B83230A@alumni.caltech.edu
Whole thread Raw
In response to problem with arrays  (Massimo Dal Zotto <dz@cs.unitn.it>)
List pgsql-hackers
> Also trying to define the _varchar or _bpchar types fails, so it seems 
> that the conversion from 6.2 to 6.4 is not possible for many data 
> types. Any suggestion?

That sucks. afaik the only data types affected are the fixed-maximum
with variable-length strings. There was a comment in gram.y from Jolly
regarding the possibility for allowing bpchar and varchar into arrays,
though she explicitly disallowed it. I had thought that this code is
still in effect.

I'm not certain how much you have looked at this, but the leading
underscore is a Postgres convention for array data types. The trick to
allowing bpchar, varchar, and perhaps numeric types into arrays is
passing along the element dimensions. I haven't looked at whether that
already happens.

In the meantime, you can try using the text type instead. I know it
doesn't have an 8-byte maximum length, but it is allowed in arrays...
                     - Tom


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [PORTS] vacuum takes too long
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] A small problem with the new inet and cidr types