I want to continue our production operations while adding a column and an index to a table that contains roughly 1.6 billion rows. It is expected that there would be a continuous stream of UPDATE and UPSERT queries on the original table while the tool is running. However, I came across an interesting observation:
The tool uses triggers to propagate any change done on the original table to the new table. Since triggers are "triggered" immediately after the query on the original table completes, what happens if an UPDATE or DELETE query is executed and the corresponding rows have not been copied yet to the new table? Am I right to assume that the tool would fail to reflect the changes on the new table once the rows are finally copied to the new table?
The tool uses triggers to propagate any change done on the original table to the new table. Since triggers are "triggered" immediately after the query on the original table completes, what happens if an UPDATE or DELETE query is executed and the corresponding rows have not been copied yet to the new table? Am I right to assume that the tool would fail to reflect the changes on the new table once the rows are finally copied to the new table?
Comment