not compatible with PG when binding insert into table with generated column

[st1page]

In RisingWave, when inserting into a table with a generated column, RisingWave automatically removes the generated column during the insert column mapping. However, PostgreSQL does not do this.

risingwave/src/frontend/src/catalog/table_catalog.rs

Lines 432 to 436 in 9dabb6e

	pub fn columns_to_insert(&self) -> impl Iterator<Item = &ColumnCatalog> {
	self.columns
	.iter()
	.filter(|c| !c.is_hidden() && !c.is_generated())
	}

RW behavior:

dev=> create table t(v1 int, v2 int AS (v1+1), v3 int default 10);
CREATE_TABLE
dev=> insert into t values (0, 1);
INSERT 0 1
dev=> select * from t;
 v1 | v2 | v3 
----+----+----
  0 |  1 |  1

PG behavior: (PostgreSQL 16.2)

postgres=# create table t(v1 int, v2 int GENERATED ALWAYS AS (v1+1) STORED, v3 int default 10);
CREATE TABLE
postgres=# insert into t values (0, 1);
ERROR:  cannot insert a non-DEFAULT value into column "v2"
DETAIL:  Column "v2" is a generated column.
postgres=# insert into t(v1, v3) values (0, 1);
INSERT 0 1
postgres=# insert into t values (0, 1, 2);
ERROR:  cannot insert a non-DEFAULT value into column "v2"
DETAIL:  Column "v2" is a generated column.