pgsql: Ignore generated columns during apply of update/delete.

2023-03-22 Thread Amit Kapila
Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber duri

pgsql: Ignore generated columns during apply of update/delete.

2023-03-22 Thread Amit Kapila
Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber duri

pgsql: Ignore generated columns during apply of update/delete.

2023-03-22 Thread Amit Kapila
Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber duri

pgsql: Ignore generated columns during apply of update/delete.

2023-03-22 Thread Amit Kapila
Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber duri

pgsql: Ignore generated columns during apply of update/delete.

2023-03-22 Thread Amit Kapila
Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber duri