From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Scaleable DB structure for counters... |
Date: | 2006-07-16 16:40:15 |
Message-ID: | 44BA6BEF.4020706@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eci Souji wrote:
> What if instead of book checkouts we were looking at how often a book
> was referenced? In which case we're talking multiple times an hour, and
> we could easily have each book requiring hundreds of thousands of rows.
> Multiply that by hundreds of thousands of books and a the table seems
> to become huge quite quick. Would breaking up the table by year still
> make sense? I'm just not familiar with having to deal with a table that
> could easily hit millions of records.
Are all 200000 books accessed every hour? What kind of library is
this? Do you have robot librarians moving at hyperspeed? Wouldn't
a more reasonable value be 5000 books per *day*?
It's easy to know when a book is checked out. How do you know when
a book is referenced? Are all books only accessed by the librarians?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEumvvS9HxQb37XmcRAg0wAKDOYZWThOFbIK3MWJw9RoD6Ql3zawCfdrBf
k3GCt4HEvMtrxfQMQM2Wv9M=
=fW2P
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2006-07-16 19:00:05 | Postgresql and Oracle |
Previous Message | Adam Witney | 2006-07-16 16:36:20 | Re: I have a questions, can you help-me ? |