Date: Wed, 19 Apr 2023 11:35:29 +0200
From: Bruno Bonfils <asyd@asyd.net>
To: pgsql-bugs@postgresql.org
Subject: About #13489
Message-ID: <ZD+14YZ4IUue8Rhi@gendo.asyd.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Archived-At: <https://www.postgresql.org/message-id/ZD%2B14YZ4IUue8Rhi%40gendo.asyd.net>
Precedence: bulk

Hello there, 

A few years ago, someone reported a bug (#13489) about attndims, which
returned a false value on an array on a table created by CREATE TABLE
<cloned_table> (LIKE <original_table> INCLUDING ALL), 

example:

CREATE TABLE test (data integer, data_array integer[];
CREATE TABLE test_clone (LIKE test INCLUDING ALL);

SELECT attndims FROM pg_attribute WHERE attrelid = 'test'::regclass AND
attname = 'data_array';

returns 1

but

SELECT attndims FROM pg_attribute WHERE attrelid = 'test_clone'::regclass AND
attname = 'data_array';

returns 0

However, according to the documentation https://www.postgresql.org/docs/15/catalog-pg-attribute.html,
since data_array is an array I expected the returned value should be
greater than 0

Thanks

(tested on PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1))