PokerTracker

I'm getting this error when I try to backup my PTO database: invalid memory alloc request size #####. Is there any fix for this? I'm posting it here because it looks like a postgre issue and this is the only postgre board I could find outside of PT3.

Also, I'm using postgre 8.2. Is an upgrade to 8.3 recommended?

Is it a huge database? I seem to remember there might be issues with backing up huge databases in PostgreSQL, once the backup reached a certain size. Do you remember what dot version of PG 8.2 this was? It is 8.2.6?

I am using version 8.2.6. I remember the problem with large databases. That happens when the backup file itself exceeded 2GB in size thus causing an error. That is not the case here as my backup file is well short of 2GB, and I believe that bug was fixed in 8.2.3 anyway.

This is a strange error because I was able to backup this database just as recently as last week. Since then I reimported all the hands fresh into an empty database to take advantage of the patch that makes separate levels for NL with cap and standard NL. So this database is the same size and is freshly created. The only thing I did to this one that I hadn't done to the original database for a while is the clustering of various indexes as described in a post you surely are familiar with. Maybe the clustering has someone screwed up the database. I guess the only way to know is to reimport all the hands again and then try to backup without clustering. I hate the thought of that as the database has 2.5 million hands and it took 3 days to import everything.

Googling this memory alloc request size error I find several hits but most of it is way to technical for me to follow. Here's one hit.
http://archives.postgresql.org/pgsql-ad ... g00117.php

I would not know how to do what they are talking about in that link, I am not that familiar with the inner workings of PostgreSQL.

Unfortunately importing the hands again into a new db is probably what you'll need to do.

Right, I'll reimport everything. The moral of this story seems to be make a backup before doing any operations like clustering.

fmny wrote:Right, I'll reimport everything. The moral of this story seems to be make a backup before doing any operations like clustering.

Yes, that's a good idea.