From: | "Jon Stewart" <jonathan(dot)l(dot)stewart(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Creating large database of MD5 hash values |
Date: | 2008-04-10 14:48:59 |
Message-ID: | c0787d8a0804100748l51b63c7fx34db59e33f13c208@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hello,
I am creating a large database of MD5 hash values. I am a relative
newb with PostgreSQL (or any database for that matter). The schema and
operation will be quite simple -- only a few tables, probably no
stored procedures -- but I may easily end up with several hundred
million rows of hash values, possible even get into the billions. The
hash values will be organized into logical sets, with a many-many
relationship. I have some questions before I set out on this endeavor,
however, and would appreciate any and all feedback, including SWAGs,
WAGs, and outright lies. :-) I am trying to batch up operations as
much as possible, so I will largely be doing comparisons of whole
sets, with bulk COPY importing. I hope to avoid single hash value
lookup as much as possible.
1. Which datatype should I use to represent the hash value? UUIDs are
also 16 bytes...
2. Does it make sense to denormalize the hash set relationships?
3. Should I index?
4. What other data structure options would it make sense for me to choose?
Thanks in advance,
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Gundy | 2008-04-10 14:52:31 | Re: varchar index joins not working? |
Previous Message | John Beaver | 2008-04-10 14:44:59 | Re: large tables and simple "= constant" queries using indexes |