New Software SpadeEye: Tableselection (@PP)

[Mr_Snood]

Unfortunately it is not possible to expand to other rooms.

The Stars support is also discarded.
The work on Tribeca will go on, but not in the next 3-4 weeks.

Didn't know that there exist Absolute skins.
I will add VegasPoker-247.

[-zero-]

Sven, is SpadeEye compatible with Postgre 8.2? PokerTracker released an update which lets you download and use Postgre8.2 instead of the old 8.0, which is much faster. I can't add these new databases to SpadeEye though, it just gives me the "Database does not exist" error. Thank you.

[-zero-]

Perhaps the problem is that you have to set the new Postgres to use a different port than the original?

[Mr_Snood]

I doubt that SpadeEye is compatible with PostgreSQL 8.2.
I got to take a look "if" and "how much" work would be needed to move to 8.2.
Besides is 8.2 downward compatible?

[Our House]

Mr Snood,

I'm in the same boat. PokerTracker released an update this week (2.16.00e) that has PostgreSQL 8.1 and 8.2 support. Many of us have already moved our databases over to the latest Postgre version; as they process the PokerTracker and PokerAceHUD queries in about 1/4 the time. The instructions on the PokerTracker forum say to use port 5433 on the install (instead of port 5432). PokerAceHUD instructed us to use the following registry entry to allow compatibility:

------------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\PTrack]
"PSQLUID"="<username>"
"PSQLPWD"="<password>"

-------------------------------------

SpadeEye is unable to connect to the databases at this point. There's no option to change for port 5433. Maybe allowing users to change the port number, or adding a registry entry like PAHUD did would be a solid work-around. At the moment, any of us who followed the PT instructions and updated PostgreSQL cannot run SpadeEye scans at all.

Thanks,
OH

[Percula]

Humm, I upgraded my linux PSQL to 8.1.x (latest stable release) and set it up for default port 5432 and setup PT to use 5432 and have no problems. PT, SpadeEye, PAHUD all working fine without having to hack the registry. I read thru several of the PT forums posts and dont remember anything saying you have to run 8.1 or 8.2 on 5433. After all you can configure PT to use what ever port you want.

There really isn't any reason to run PSQL on 5433 unless you are retaining your 8.0.x server on port 5432 in addition to 8.1 or 8.2 server on another port. And you could change your 8.0 server to use 5433 by editing your postgresql.conf file too if you have to retain your 8.0 server instance.

[Our House]

Percula,

Thanks for the information. I don't need to retain PGSQL 8.0, but I did set 8.2 up on 5433 as suggested in the PT forum.

Can you elaborate on how to change the port on 8.1/8.2 back to 5432? I've tried removing it from PT and re-adding it on 5432, then editing the ODBC data source settings, and finally changed the properties in PGAdminIII. PT didn't like those changes (DB errors came up) and I never tried changing the postgresql.conf file.

Any help would be appreciated before I attempt this again and possibly screw it up. Thanks.

[Percula]

Our House,

The postgresql.conf file is just a plain old text file. Open it in notepad, wordpad, etc then look for this section near the top...

[ QUOTE ]
#---------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#---------------------------------------------------------------------------

# - Connection Settings -

listen_addresses = '192.168.100.90' # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost', '*' = all
port = 5432
max_connections = 100
....


[/ QUOTE ]

Then change the port from 5433 to 5432 and restart the PSQL service.

[Our House]

That worked, Perc. Thank you! I needed to take some of the other steps from my earlier post.

A few things to note (for others who need to do this):

- Stop the PostgreSQL service
- Change the port# to 5432 in the postgresql.conf file
- Remove the PostgreSQL settings in PokerTracker and add them again under port# 5432
- Go to the ODBC datasources (System DSN tab) and edit all of the unicode databases and the unicode test port so that they are also at port# 5432
- Enter the PGAdminIII tool from the start menu (under PostgreSQL) and change the properties of the 8.1/8.2 Database Server so it works from port# 5432
- Restart the PostgreSQL service

** If PokerAceHUD doesn't update stats correctly (mine didn't), then just close BOTH PAHUD and PokerTracker, run the registry editor from my above post, and reopen them.

That should do it.

[Our House]

Sven,

It seems like the port was the issue. At the moment, SpadeEye requires the user to operate on port 5432. Adding a Databases Tab option to change ports would allow the users who have several versions of PostgreSQL to use SpadeEye on any of them.