On 04.08.2020 18:18, Stephen Frost wrote:
Independently while considering this, I don't think the issues around
how to deal with unique btrees properly has really been considered- you
certainly can't stop your search on the first tuple you find even if the
index is unique, since the "unique" btree could certainly have multiple
entries for a given key and you might need to find a different one.
But search locates not ANY record with specified key in top index but record
which satisfies snapshot of the transaction. Why do we need more records
if we know that
there are no duplicates?
