I have force-pushed my alternate attempt after adjusting it slightly.
It is now taking < 30 minutes reliably on our database server, and my last test run (where the data was, I believe, no longer only on disk, having rolled back a previous test run) took just over 15 minutes.
The database I tested in has 3,953,845 rows in action.circulation.
I have force-pushed my alternate attempt after adjusting it slightly.
It is now taking < 30 minutes reliably on our database server, and my last test run (where the data was, I believe, no longer only on disk, having rolled back a previous test run) took just over 15 minutes.
The database I tested in has 3,953,845 rows in action.circulation.