converting

PostgreSQL is the database server used to store information. Do you have a question or are you having problem with PostgreSQL? If so, post them here.

Moderator: Moderators

converting

Postby zedjr » Fri Feb 15, 2008 5:18 pm

I have sql 8.2 installed on drive K and pt2 uses this. I have sql 8.3 for pt3 installed on drive L. I have the os on drive C. PT3 does not recognize databses on drive k which is the 8.2 databses from pt2. AM trying to convert. What shall i do? One more additional piece of info is that 8.2 is on port 5432 and 8.3 port 5433.
zedjr
 
Posts: 198
Joined: Mon Feb 04, 2008 6:28 pm

Re: converting

Postby zedjr » Fri Feb 15, 2008 5:26 pm

Another question is pt3 actaully usable. HAve been messing with this for a few hours. AM jsut coming to a dead end on alot of things. Will poker ace now read my new pt3 sql 8.3 db. I first need to restore. I am thinking htough maybe i should wait till this is actually usable app. I dont see any restore options or back up options
zedjr
 
Posts: 198
Joined: Mon Feb 04, 2008 6:28 pm

Re: converting

Postby Josh » Fri Feb 15, 2008 5:51 pm

I'll let Derek work with you on your PostgreSQL issues. He's more familiar with it than I am. As for PT3 being usable, yeah, but it does have limitations due to things not yet being implemented. This is an early beta. If you want to work with a completed application, you should wait until the commercial release.
Josh
Site Admin
 
Posts: 6222
Joined: Sat Dec 08, 2007 6:03 pm

Re: converting

Postby APerfect10 » Fri Feb 15, 2008 6:56 pm

I would imagine that you can run both 8.3 and 8.2 simultaneously on different ports. I am not sure. Are both the 8.2 and 8.3 Database Servers started? You will need to handle each of them separately. IMHO, I would stick with 8.2 and use that with both PT2/PT3. Once PT3 is ready for final release and you can ditch PT2 then I would convert to 8.3

Best regards,

Derek
APerfect10
Site Admin
 
Posts: 4464
Joined: Sat Dec 08, 2007 6:03 pm

Re: converting

Postby Hercules » Fri Feb 15, 2008 7:03 pm

had the same issue here.. I edited the PokerTracker.cfg file.
Manually changing the Default.Postgres.* fields did the trick for me.
Hercules
 
Posts: 78
Joined: Fri Jan 25, 2008 2:38 pm


Return to PostgreSQL [Read Only]

Who is online

Users browsing this forum: No registered users and 16 guests

cron