At the moment, after_import scripts are executed every time we run runimporters, whether or not there is any new data imported.
Consider if this is the correct behaviour (at the moment it means materialized views are always refreshed, which is very slow, and in particular not necessary if the script had been interrupted for some reason)
The main reason for this issue was to avoid running matviews uncesssarily; I think this is better fixed by making them depend on the prescribing data import per cb437c49a04e4dc0f3d08125110ba325b695926f
At the moment,
after_import
scripts are executed every time we runrunimporters
, whether or not there is any new data imported.Consider if this is the correct behaviour (at the moment it means materialized views are always refreshed, which is very slow, and in particular not necessary if the script had been interrupted for some reason)