|
|
|
|
|
|
by nh2
393 days ago
|
|
|
> or make sure that the Session ID field is indexed with a hash-based index Using a hash index instead of a btree isn't a 100% guaranteed solution because there may be craftable collisions (because e.g. postgres's index hash is not cryptographic) which cause fallback to linear comparison across the values inside the hash bucket: https://dba.stackexchange.com/questions/285739/prevent-timin... So hashing the ID before the DB lookup is better. |
|
|