Re: Identical servers different plan for the same query

[Eric Coll]

Answering the index questions:

The last_tiemstamp table and join are correct. This table register the latest snapshot per region. Basically, the most recent data for all accounts in that region will have the same timestamp.

The unique key is awful, agree, but I understand why it was done like that. The partitioned table requires a unique index and that was the only unique key. I'd have replaced have of the fields with a generated id or a hash, but that requires significant changes to the live db and the services that insert the data which are fairly complex.