Problem: the implementation of that `WHERE` filter is too inefficient. In particular this was brought to attention because it causes `Explorer.Etherscan.list_internal_transactions/2` to timeout for some addresses. (For example: address `0x1B3858E01CCE5d0491f3c96A9996a65607f3493b`) Solution: while keeping the same result the previous check for siblings (SELECT/LIMIT 2/COUNT/(> 1)) has been replaced by a less expensive one that better uses the existing indexes (EXISTS/index comparison).pull/2267/head
parent
3c6abf4d23
commit
453d04244e
Loading…
Reference in new issue