Re: pg_upgrade fails to detect unsupported arrays and ranges - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: pg_upgrade fails to detect unsupported arrays and ranges
Date
Msg-id 11F789E7-EEF1-40C6-97CF-1D8F3B4BB66F@yesql.se
Whole thread Raw
In response to Re: pg_upgrade fails to detect unsupported arrays and ranges  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 10 Nov 2019, at 22:05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:

>>> +        /* arrays over any type selected so far */
>>> +                          "            SELECT t.oid FROM pg_catalog.pg_type t, x WHERE typelem = x.oid AND typtype
='b' " 
>
>> No need to check typlen?
>
> Yeah, that's intentional.  A fixed-length array type over a problematic
> type would be just as much of a problem as a varlena array type.
> The case shouldn't apply to any of the existing problematic types,
> but I was striving for generality.

That makes a lot of sense, thanks for the explanation.

cheers ./daniel


pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: psql \d for wide tables / pattern for individual columns
Next
From: Daniel Gustafsson
Date:
Subject: Re: pg_upgrade fails to detect unsupported arrays and ranges