Erik Johnston 483ba85c7a Analyze user_ips before running deduplication ... Due to the table locks taken out by the naive upsert, the table statistics may be out of date. During deduplication it is important that the correct index is used as otherwise a full table scan may be incorrectly used, which can end up thrashing the database badly.		2019-02-12 11:55:27 +00:00
..
12	…
13	…
14	…
15	…
16	…
17	…
18	…
19	…
20	…
21	…
22	…
23	…
24	…
25	run isort	2018-07-09 16:09:20 +10:00
26	…
27	run isort	2018-07-09 16:09:20 +10:00
28	…
29	…
30	run isort	2018-07-09 16:09:20 +10:00
31	run isort	2018-07-09 16:09:20 +10:00
32	…
33	run isort	2018-07-09 16:09:20 +10:00
34	Drop sent_transactions	2018-12-01 23:07:35 -06:00
35	…
36	…
37	run isort	2018-07-09 16:09:20 +10:00
38	…
39	…
40	Add unique indexes to a couple of tables	2018-11-02 10:36:13 +00:00
41	…
42	run isort	2018-07-09 16:09:20 +10:00
43	…
44	…
45	…
46	WIP e2e key backups	2018-09-13 17:02:59 +01:00
47	…
48	…
49	…
50	api into monthly_active_users table	2018-07-31 16:36:24 +01:00
51	Don't reuse backup versions	2018-10-05 15:08:36 +01:00
52	Merge remote-tracking branch 'origin/develop' into dbkr/e2e_backup_versions_are_numbers	2018-11-09 18:35:02 +00:00
53	Analyze user_ips before running deduplication	2019-02-12 11:55:27 +00:00