Backtrack on min/max id - it should correspond to in-memory messages only

It is not efficient to lookup (from the db) the min/max ids for a specific channel.

MinMaxPairs will now contain both min/max id *and* date.