Postgres Pro
Downloads
Home   >   mailing lists

hash as an search key and hash collision - Mailing list pgsql-hackers

From Andy Fan
Subject hash as an search key and hash collision
Date
Msg-id CAKU4AWrhg3=fNnzc+wzO-0Or7Ot3hiKUu8N4draJ=6ZbqWJbBA@mail.gmail.com
Whole thread Raw
Responses Re: hash as an search key and hash collision
List pgsql-hackers
Tree view
I want to maintain an internal table which the primary key is sql_text and 
planstmt::text, it is efficient since it both may be very long.  So a general
idea is to use sql_hash_value and plan_hash_value. Then we have to
handle the hash collision case.  However I checked the codes both in sr_plans[1]
and pg_stat_statements[2],  both of them didn't handle such cases, IIUC.  so
how can I understand this situation?  



--
Best Regards
Andy Fan

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Review for GetWALAvailability()
Next
From: Fujii Masao
Date:
Subject: Re: min_safe_lsn column in pg_replication_slots view