Re: Scaleable DB structure for counters...

I think "books" may have thrown everyone for a loop.  These are not
physical books, but rather complete scanned collections that would be
available for search and reference online.  One of the most important
features required would be keeping track of how often each book was
referenced and when.  Time of day, days of week, etc.  This is why I was
looking into how to construct some form of counter system that would
allow us to keep track of accesses.

Although I would love to see a robot librarian at work.  :-)

- E

Ron Johnson wrote:
> -----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-----
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faq
>