Should certification primary key contain block number?

When looking at Duniter Indexer, I saw that the set of columns (receiver_name, issuer_name) was set as the primary key for certification table. In my understanding, this prevents the indexer from remembering renewed certifications as a new certification A → B on block 8000 can not coexist with a previous certification A → B on block 4000.

@ManUtopiK can you confirm this? Should we add the block number to the primary key?