Problem with Rebuilding Cache

[Mr Tiger]

I've sent a ticket to support team with this issue. But on the forum I usually receive answers very fast, and this issue is very urgent. So I post here too.

Recently I've made a lot of new columns in "Holdem Cash Player Statistics" section. When I tried to rebuild the cache then, I got this message: "........Fatal Error (ERROR: tables can have at most 1600 columns )". Then I removed all columns (and later all stats) and import my previously saved HUD profile with stats I need. I counted the columns: total number incl. not default stats was <1200 under holdem cash player statistics section. However the problem still had place. But this time the error message emerged after rebuilding cache ends. Then I removed all custom stats again (now by deleting "StatDefinitionsCustomized.pt3" file) and tried to rebuld the cache. Cache was rebuilt successfully. And then I discovered that most of my columns are under omaha cash player statistics section (I never made omaha stats). And there are around 1800 columns.

So, what I plan to do:

1) Remove excessive stats from my "reserve HUD profile".
2) Export this profile.
3) Delete StatDefinitionsCustomized.pt3 file.
4) Import my "reserve HUD profile".
5) Check if there are <1600 columns.
6) Convert all stats from omaha hand player statistics section to holdem hand player statistics section.
7) Start rebuilding the cache.

The questions:

1) Is there an easier solution?
2) How this limit (1600 columns) is calculated: it must be maximum 1600 columns under one section, group of sections or under all sections including cash hand and other and tournament sections (all 16 sections)? So do I need to delete all omaha custom columns after converting them to holdem?
3) Is it possible to convert all "omaha" stats to "holdem" stats not one by one. I have a lot of stats.

[Mr Tiger]

Got answers on #2 and #3 questions (max 1600 per section; have to convert stats one by one) in the ticket. So, I'm going to implement my plan.

[kraada]

The Omaha and Holdem cache are separate in PT3 so they each have their own maximum. The 1600 column maximum is a PostgreSQL limitation and unfortunately we cannot change that.

You cannot convert stats en masse either I'm afraid, but your plan should work. Good luck.

[Mr Tiger]

Found this thread in my bookmarks... Just want to say, that things were better than I thought. I just needed to import (to my second computer) HUD profile instead of individual groups. In this case there were no problems. And the amount of columns were 1594. Lucky :)

[kraada]

I'm glad to hear it :)