backfill reports_clean for 2012-07-31

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: rhelmer, Assigned: rhelmer)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

6 years ago
Something I should have remembered earlier - since the reports_clean job wasn't running correctly until we pushed 17.4 earlier today, the data won't be correct when the daily_matviews job runs (I double checked and the reports_clean rollback was successful, so this is a one-time thing).

I went ahead and started this now, so it'll be done by 2 AM PDT (which is when daily_matviews runs):

breakpad=> select backfill_reports_clean('2012-07-31','2012-07-31');
(Assignee)

Comment 1

6 years ago
(In reply to Robert Helmer [:rhelmer] from comment #0)
> Something I should have remembered earlier - since the reports_clean job
> wasn't running correctly until we pushed 17.4 earlier today, the data won't
> be correct when the daily_matviews job runs (I double checked and the
> reports_clean rollback was successful, so this is a one-time thing).
> 
> I went ahead and started this now, so it'll be done by 2 AM PDT (which is
> when daily_matviews runs):
> 
> breakpad=> select backfill_reports_clean('2012-07-31','2012-07-31');
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 00:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 01:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 02:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 03:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 04:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 05:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 06:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 07:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 08:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 09:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 10:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 11:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 12:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 13:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 14:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 15:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 16:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 17:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 18:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 19:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 20:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 21:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 22:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-07-31 23:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-08-01 00:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-08-01 01:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-08-01 02:00:00+00
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-08-01 03:00:00+00
 backfill_reports_clean 
------------------------
 t
(1 row)
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.