Page 1 of 1

Successfully created a DB on a 'server' and not on localhost

PostPosted: Sun May 04, 2008 5:09 pm
by Klimpen717
I have some issues with running PostgreSQL on my main machine since it is also used as a testrig for hardware and overclocking.
That means it is not always running or that it has crashed about a zillion times during the last week of overclocking or testing out new hardware.
It is also a constant reinstalling of Windows and testing different operatinsystems on it.
I wanted a solution where my important Pokertracker Database was stored and maintained on another machine, my SERVER :D
As I have searched the forums I have found no way of doing this.
So now I wonder:

1. Have there been a solution for this
2. Is there anyone interesting in a solution (my solution)

If the answer to #1 is YES, please point me over there so I can help out, and we can close this thread.
If NO to #1 and YES to #2 then I will start explaining in this thread.
I won't just spend an hour to explain now if there is already a solution or/and there is no one interested 8-)

Re: Successfully created a DB on a 'server' and not on localhost

PostPosted: Sun May 04, 2008 11:45 pm
by APerfect10
You simply install PostgreSQL on your server then point PokerTracker 3 to it via the connection manager...

Best regards,

Derek

Re: Successfully created a DB on a 'server' and not on localhost

PostPosted: Mon May 05, 2008 3:59 pm
by Klimpen717
Where do I find the Connection Manager?
Are you sure you can just point your local PT3 to connect to a database that is not 'localhost'
AFAIK the PostgreSQL wont by default accept connections from a 'foreign host' without some editing to the
postgresql.conf and pg_hba.conf.

Re: Successfully created a DB on a 'server' and not on localhost

PostPosted: Mon May 05, 2008 10:04 pm
by _dave_
Klimpen717 wrote:AFAIK the PostgreSQL wont by default accept connections from a 'foreign host' without some editing to the
postgresql.conf and pg_hba.conf.


heh, I just PMmed to get this added to the new FAQ pages :)

You will need to edit pg_hba.conf - and add the IP address of the remote computer with either "md5" or "trust" authentication, before it will allow access.

You can add a range if you use DHCP too, by changing the /32 on the end to a lower number, like /24 (for whole last octet allowed) - I wouldn't do this unless you have total faith in the security of your network, IE it is private and hard-wired (no wireless!)

highfalutin