Column name checks are too strict

CrunchyData / pg_parquet

Copy to/from Parquet in S3 from within PostgreSQL

Other

358 stars 11 forks source link

Column name checks are too strict #39

Open onderkalaci opened 1 month ago

onderkalaci commented 1 month ago

I think we should not care much about the column names, we already check the column types, which is fine.

 create table t1(a int);

 insert into t1 VALUES (1);
 copy t1 to '/tmp/data.parquet';

create table t2(b int);
copy t2 from '/tmp/data.parquet';
ERROR:  column "b" is not found in parquet file