Kostas Dermentzis

Is this for 13.1.0.0.? Many things have vhanged there related to indexes and unique keys

In `13.1.0.0` most unique keys are removed and most indexes are create after syncing has almost completed. Possible there are still unecessary indexes though that take space. Btw `13.0.4` has...

Related https://github.com/input-output-hk/cardano-db-sync/issues/1233

This error message could indicate that the node is behind and block for some seconds, so that the fail loop doesn't happen that often.

This is fixed on `13.1.0.0`. Shoul we close @ArturWieczorek?

Could you provide a more spicific example which was inconsistent? Btw there are newer release with a number of improvements, butr afaik nothing related to Epoch Param, Epoch Stake

As documented in https://github.com/input-output-hk/cardano-db-sync/blob/master/doc/schema.md#epoch_stake the `epoch_stake` table is populated incrementally in the first blocks of each epoch. So the result of this query is not stable until the epoch changes...

Possibly duplicate of https://github.com/input-output-hk/cardano-db-sync/issues/1349. Since adding indexes helped, maybe we can close?

I think this comment applies here https://github.com/input-output-hk/cardano-db-sync/issues/1349#issuecomment-1490354022 Clients should be responsible to add the indexes that they need.

This is described in https://github.com/input-output-hk/cardano-db-sync/blob/master/doc/migrations.md#upgrading-to-13100 Basically with 13.1.0.0 we splitted existing indexes to two groups. The stage 3 migration, which are indexes created at the beginning and are crucial for...