PT3 db archiving tips

[Parket]

I'm still on one single database ever since I started a couple of years ago.
Are there any useful tips on archiving historical data ?

I was thinking of keeping a separate database per full year prior to 2011. My main db would then only have everything after Jan.1 2011.
* Is it possible to compress databases in postgresql for archiving purposes (as no inserts are required anymore) ?
* And what would be the most time/diskspace effective approach ? The only thing I can think of is to first entirely copy my main database, and then purge everything that is not in the target year. And repeat this for every year. And finally then purge everything prior to 1/1/2011 from my main database. Sounds like a lot of disk activity though...

[kraada]

It's going to be a considerable amount of work no matter which way you slice it. PostgreSQL doesn't have any sort of compression for static databases that I'm aware of. Your duplicate then purge method will work - another method would be to export your hands from just a given year, then import those to a new database for that year and repeat for as many years as you need. Then in the end purge your master database down to one year (probably 2011 is best - for 2012 starting a new database is easy still).

[WhiteRider]

If you have any large number of hands exporting and importing to new databases will be significantly faster then duplicating and purging.
Personally if I was going to split it like that I'd import to a new database for each section - if you have the original hand history files import from those as a preferred option, but otherwise from exports should be fine too. I wouldn't even purge down to the final database - I'd do that as an import to a new database too. That will almost certainly be faster.

[Parket]

Does an export also take all tournament results ?
Re-importing HH files is a no-go as I always manually corrected things like buy-in, tournament type, rebuys/addons... So I absolutely want to preserve all that information when moving to a new database.

[WhiteRider]

Ah yes, of course - for tournaments an export/import will be better as that will write out all the detected and manually updated information to summaries which can be re-imported.

[Parket]

There seems to be a memory leak in PT3 which makes exporting a large piece of my database impossible without PT3 crashing. I filed a ticket for this : 116292 .
For now, I have to take small enough chunks (1 month) to avoid the crashes, which of course means quite a bit of work.

Also: when I have export-files, where do I import those straight into PT4 ? I can't find any Import option (in fact, can't find it for PT3 either).

[Parket]

Nvm the Import question. Have found it myself now (PT4: Play Poker - Get Hands From File).

[WhiteRider]

Thanks - we'll get back to you via your ticket.