RdLrT
RdLrT
Tho reward.id was intentionally dropped in PR #1607 ?
While the immediate task as put aptly by @kderme is 'to have a policy that stops fetching attempts when there is a newer pool update' , a side-action/question here is...
Unless this is about replacing tx table altogether, it brings little benefit (definitely not from performance pov, as looking at an indexed hash has higher resource cost than tx_id field...
@kderme - Docker's restore snapshot function was broken at 13.6.0.5, it is fixed on main but we dont have a tag since
tx_out.stake_address => that would have negative impact (similar reasoning as recently split out address table), moreso for stake_address as it's referred across a lot of tables.
Sure, just weighing pros/cons, I am still unclear how would this work then for all the stake address references across tables (from query pov, the joins will still need to...
You'd want to pass environment variable SUDO=N on your setup.
This instance is on mainnet & was created on 7th January and was already on 13.6.0.4 using a snapshot from another instance (which is same base snapshot used for majority...
@Cmdv - Wouldnt that occur across all instances that the snapshot was restored on? In this case, there are - in fact - two specific machines that go through upgrades...