Hi
I found an exception using the latest master branch of PGSQL and wanted to check if it was a bug
Please refer this below scenario
1)initdb ./initdb -k -D data
2)Connect to server using single user mode ( ./postgres --single -D data postgres) and create a table ./postgres --single -D data PostgresPostgreSQL stand-alone backend 13develbackend>create table t_create_by_standalone(n int);
--Press Ctl+D to exit
3) use pg_ctl start database
4) use psql connect database, and create a table
create table t_create_by_psql(n int);
5) check the pg_type info
postgres=# select oid,relname,reltype from pg_class where relname like 't_create%';
oid | relname | reltype
-------+------------------------+---------
13581 | t_create_by_standalone | 13582
16384 | t_create_by_psql | 16386
(2 rows)
postgres=# SELECT oid,typname, typarray FROM pg_catalog.pg_type WHERE oid in (13582,16386);
oid | typname | typarray
-------+------------------------+----------
13582 | t_create_by_standalone | 0
16386 | t_create_by_psql | 16385
(2 rows)
Use single user mode (t_create_by_standalone) typarray = 0, but use psql t_create_by_psql typarray has oid.
Is there something wrong to have different catalog information with the same sql?
