13M rows in the history table (in General)

Think I'd better have a look.

First and what?

Second and huh?

you know, the data that CB uses to draw those pretty graphs

How quickly is it growing?

Perhaps keep the last X days of real data, then only record a trend or average number for each previous $timeperiod. Say... daily for the last 90 days, and a weekly average for previous dates?

Wow, give your db server a hug from me, 13m rows and it doesn't cough and die on a request?

Hell of a coding job Jon.

nah, it's smarter than that

only I was doing min() instead of max(), oops.

postgresql is tough enough to withstand even stupid mistakes like that one :P

it was starting to play hell with the cache though, which is what made me suspicious

Yes I've started to consider pqsql instead of mysql on a couple of coming jobs, the only issue is the person who will maintain the DB hasn't a clue on pgsql.

And they are not paying me enough to teach him anything.

Hell of a coding job Jon.

--mrwuss, 11:50 AM EDT

I would have to agree. I wish some other game developers would drop by the site and take some notes. :)

pgsql doesn't need "maintenance," it's not like Oracle that way... if you let apt install it on debian it even sets up autovacuum for you.

you would want to spend half an hour or so going through postgresql.conf and increasing the amount of memory you let PG grab for various activities, though. the defaults are excessively conservative.

then again if your app is small enough you might not even need to bother with that much.