Historical prices data is available in both pair specific tables named
prices.[Token0]_[Token2] (e.g. prices.btc_usdt) or in a single table containing all pairs named
prices.all_pairs, which has an extra
pair column to. For better performance, we recommend using the pair specific tables when you know the pairs that need to be queried at compile time and using the single table of all pairs when the pairs that need to be queried are determined dynamically at runtime.