About #13489 - Mailing list pgsql-bugs

From Bruno Bonfils
Subject About #13489
Date
Msg-id ZD+14YZ4IUue8Rhi@gendo.asyd.net
Whole thread Raw
Responses Re: About #13489, array dimensions and CREATE TABLE ... LIKE
List pgsql-bugs
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))




pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger
Next
From: PG Bug reporting form
Date:
Subject: BUG #17903: There is a bug in the KeepLogSeg()