| Description | Big tables can cause issues during an initial load because a load is in a single transaction. One possible solution that has been thrown around is to download the initial load to a file before loading it into the database. This would allow a load to be recoverable even with commit strategies other than 'load everything in one transaction.' This would also allow an extension point to use database specific load utilities. As part of this issue we might also think about moving initial loads to be on the same channels that synchronization happens on so that synchronization stops when an initial load fails. |
|---|