Clustering possibly caused C drive to fill up

Experiencing technical difficulties? Think you've found a problem with PokerTracker 3? Report it here.

Moderator: Moderators

Re: Clustering possibly caused C drive to fill up

Postby Wada » Mon Jan 28, 2008 10:09 pm

I have 20 gigs on drive D. PostgreSQL is installed on C and PokerTracker 2 and 3 are on drive D.

Now I just went to Start > Programs > PostgreSQL 8.2 > pgAdmin III.

I opened it and noticed both 8.0 localhost: 5432 and 8.2 localhost: 5433 had a red X under the Servers.

I right click and clicked on Connect. it asked for the password. I entered the password for both 8.2 and 8.0.
The red X went away and it connected.

next I opened up PT2 and got my database and am able to see hands played on 1/24/08 which all seems to be good.

Next I reopened the pgAdmin III and the red X are there again. (Is this a problem?) I closed out PT2 and reopened it and did not have problems.

What do I do about all those damn files in the 8.2\data\base\##### folders?
Wada
 
Posts: 8
Joined: Thu Jan 24, 2008 11:48 pm

Re: Clustering possibly caused C drive to fill up

Postby _dave_ » Mon Jan 28, 2008 10:12 pm

Thise files are the binary information that comprises your data base - the clue is in the file path :)

You are lucky you have all your PT2 data in a postgres installation (in another folder) by the sounds of things, so it avoided the culling.

The red "X" just means disconnected - whenever you start pgAdmin you have to double-click on a server to connect - so don't worry about those.

I'd suggest manually installing postgres 8.2 to the D: drive, then instructing PT3 to use that as a data base.
_dave_
 
Posts: 1147
Joined: Sun Dec 09, 2007 6:19 pm

Re: Clustering possibly caused C drive to fill up

Postby Wada » Mon Jan 28, 2008 10:26 pm

8.0 folder is like 33.9 megs and thats it.
8.2 folder is like 7.94 gigs!

I still have one folder sitting in the recycle bin that has not been restored. So what you are saying is there is a possibility that the folder pertains to some information through out the entire database and that 7.9 gigs is about right for a 600k hand history database?

How do i go about making this change over to drive D with out making matters worse?
Completely install PostgreSQL 8.2 on Drive D? Then how do I get the Drive D to connect to or link to PT2 and PT3? this is confusing. Should I start with the same methods posted :http://pokertracker3.com/forums/archives/PT2/viewtopic.php?t=6310
Wada
 
Posts: 8
Joined: Thu Jan 24, 2008 11:48 pm

Re: Clustering possibly caused C drive to fill up

Postby _dave_ » Mon Jan 28, 2008 10:51 pm

PokerTracker 3 links to the postgres database on the IP address/port specified during setup - physical location is unimportant (personally I use a different computer)

So if you install postgres on your D: drive, that is where it will store the database files.

9GB is large for a 600K database, but not silly - If you interrupted a cluster (by running out of disk space or whatever) that would explain it.

There is no way of telling which of the number ### files pertain to which database - postgres uses it's own sort of filing system within these randomly named files.

I'd keep PT2 on postgres 8 and PT3 on 8.2 - that is what I actually do :)

If there's *certainly* no PT2 data in the postgres 8.2 database (I wouldn't be sure, seeing the small size of your 8.0 database) - just delete it and get 8.2 installed on D: - but OMG tread with care, and don't delete any more files you're not sure what they are! :)
_dave_
 
Posts: 1147
Joined: Sun Dec 09, 2007 6:19 pm

Re: Clustering possibly caused C drive to fill up

Postby Wada » Mon Jan 28, 2008 10:56 pm

Okay, for sure I wont be deleting files!

I had 8.0 originally for PT2. Then I upgraded to 8.2 and have been using 8.2 ever since, hence PT3 on port 5433.

Now I want to install it on drive D. I just did a backup of my database through Utilites > PostgreSQL Database Functions > Backup.

Now, can I install another PostgreSQL on drive D before Uninstalling the one on drive C?

Also, if I install on Drive D, what do I need after to get the PostgreSQL 8.2 on Drive D to be working with PT2/PT3 and get it to no longer work with the one on drive C? (does this make sense)

And then finally once PT2/3 is working with the PostgreSQL 8.2 on drive D, how to i go about removing it from drive C?

Thank you very much Dave, you have been very helpful.
Wada
 
Posts: 8
Joined: Thu Jan 24, 2008 11:48 pm

Re: Clustering possibly caused C drive to fill up

Postby _dave_ » Mon Jan 28, 2008 11:00 pm

[quotemlb]
Now, can I install another PostgreSQL on drive D before Uninstalling the one on drive C?
[/quotemlb]

I guess you just install it again, and choose D:\somewhere as the install path

[quotemlb]
Now, can I install another PostgreSQL on drive D before Uninstalling the one on drive C?
[/quotemlb]

Again I guess so - just use a different port - 5434?

[quotemlb]
Also, if I install on Drive D, what do I need after to get the PostgreSQL 8.2 on Drive D to be working with PT2/PT3 and get it to no longer work with the one on drive C? (does this make sense)
[/quotemlb]
Just the port the D: installed server is recieving requests on.
_dave_
 
Posts: 1147
Joined: Sun Dec 09, 2007 6:19 pm

Previous

Return to Technical Support / Bug Reports [Read Only]

Who is online

Users browsing this forum: No registered users and 18 guests

cron
highfalutin