Re: BUG #14521: pg_attribute.attndims = 0 for array column

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: krzysztof(dot)heim(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14521: pg_attribute.attndims = 0 for array column
Date: 2017-02-01 14:25:13
Message-ID: 3792.1485959113@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs

krzysztof(dot)heim(at)gmail(dot)com writes:
> I have base table A with column type integer array.
> I also have table B derived from table A.

> When I query pg_attribute for table A, attndims shows 1 (correct), when I do
> same query for table B - attndims shows 0 for same column.

> Is it a bug, or it's desired behavior (since it's a derived column).

We don't really care. attndims is a historical leftover and should never
be relied on for any semantically significant purpose.

TBH, my inclination would be to remove the column altogether rather than
"fix" this.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-02-01 15:13:18 Re: BUG #14521: pg_attribute.attndims = 0 for array column
Previous Message krzysztof.heim 2017-02-01 10:23:03 BUG #14521: pg_attribute.attndims = 0 for array column