I'm facing a problem here: our business requires logical data replication to
other departments, but at the same time, sensitive fields need to be filtered
out. Therefore, we used the column filtering function when creating logical
replication. If we use `alter table table1 replica identity default;`, there is
no issue at all. However, when encountering new business scenarios, we need to
use the CSI columnar index function. Under the default setting, the
synchronization delay of the CSI columnar index is severe. Therefore, we need
to use `alter table table1 replica identity full;` so that the CSI columnar
index can perform data comparison and only convert changed data when receiving
data, thereby speeding up the data conversion efficiency of the CSI columnar
index. However, after using `alter table table1 replica identity full;`,
updating the table will result in an error. ERROR: cannot update table "table1"
DETAIL: The column list used by the publication does not cover the replica
identity. So, is there any solution to this problem, or is there a better
approach to accelerate the conversion efficiency of the CSI columnar index.
