From: | Bruno Bonfils <asyd(at)asyd(dot)net> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | About #13489 |
Date: | 2023-04-19 09:35:29 |
Message-ID: | ZD+14YZ4IUue8Rhi@gendo.asyd.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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))
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2023-04-19 10:26:13 | BUG #17903: There is a bug in the KeepLogSeg() |
Previous Message | Richard Guo | 2023-04-19 08:29:08 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2023-04-19 09:41:08 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |
Previous Message | Hayato Kuroda (Fujitsu) | 2023-04-19 09:30:46 | RE: Time delayed LR (WAS Re: logical replication restrictions) |