Arunprasad Rajkumar
Arunprasad Rajkumar
Hmmm, I think the alternative approach is the right one.
@dimitri, Should we really worry about replica triggers? Other option would be just eliminating the IDENTITY column and revert the duplication removal, as we already have the generated column infra.
@dimitri In this PR, I'm skipping the UPDATE stmt when all columns in SET clause are duplicates of WHERE clause values. Once we fix https://github.com/dimitri/pgcopydb/issues/844, we shall also remove the...
@dimitri Thanks for reviewing this PR. > I think we should add some mention of what we're doing here in the docs. I don't think we should add to the...
> @arajkumar Could you please review my code when you get a chance. I see the following comment is not addressed yet. https://github.com/dimitri/pgcopydb/pull/849/files#r1693158692
Nice work @VaibhaveS and @Kesarwani-aditi ! Thanks @dimitri for your early work on this.
@fabriziomello @gayyappan Added tests covering drop_chunk, DROP TABLE _chunk, TRUNCATE hypertable, merge_chunk, and split_chunk.
The failure is from the following step. ``` - name: Check that no new internal program errors are introduced # We collect the same messages when uploading to the CI...
@fabriziomello @gayyappan PTAL.