Most recent record in epoch table broken after rollback-to-slot

[josef0xb]

We used rollback-to-slot function (mainnet, to slot 171,676,766 - to this slot was created one of snapshots).

It almost worked fine, but discovered some invalid data for epoch table.

Table blocks contains valid number of blocks etc. Looks like only epoch table is broken.

I tried this function on test env 3 times for a few records and it seems it is too broken, so not one-time issue.

[Cmdv]

Yes that is right, this is a bug because when db-sync has reached the tip and is following we update the epoch table every block we convert.

This overwrites the previous value in the row for that epoch. Thus when a user manually rolls back there is no historical data for each value inserted into the epoch row.

We're going to investigate a solution to this so the epoch table updates to the correct values given the rollback point