reading databases from networked computer?

[downbytheriver]

Is there any way for the purpose of table tracker and HUD i can read a database from a locally networked computer? Say i have one machine that is my playing machine and has my database and another machine that is a fulltime datamining machine, can i have PT3 read that database from my playing that is on the DM machine?? how would i go about doing this, or do you have any suggestions to achieve this task/
thanks!

[WhiteRider]

See this post: How To: Network PostgreSQL Database

[downbytheriver]

thanks whiterider!

[mjr161]

How does this change if the postgres db is hosted on a networked computer on mac osx? My playing computer is also on mac os, but I use VMWare Fusion with Win XP, which is setup with NAT between the vm and host.

My local machine is a quad Xeon 3ghz with 5gb of ram. I've dedicated 1gb to the VM and PT3 seems to really drag at times. Would networking the db take the stress off the local machine and put the strain on the server instead... which is a box that sits in my closet pretty much to serve up filesharing and some media but otherwise pretty underutilized.

[kraada]

Those directions should work fine regardless of the operating system of the server.

It will definitely take some strain off of your playing computer, but you want to make sure the server has a good chunk of hard drive space and at least reasonably fast hard drives as the DB utilizes a lot of disk i/o. So long as the server has reasonably new (read 7200rpm SATA drives or better) hard drives, it would definitely reduce the strain on your playing computer and the server would be able to hold up its end well enough to not add a new source of lag there.

Also: PostgreSQL is more efficient on linux/unix servers just because it was built for them first and Windows support was added afterwards, so you'd probably get a slight boost from that as well.

[mjr161]

Another question relating to my post above...

Ok so on my playing computer I now have 2 XP Vm's running, both with PT3 installed. Am I able to share the networked DB between both VMs and have both of them running and auto importing at the same time into the same db? The db is hosted on a networked computer installed on OSX Leopard. I don't want to make the db puke all over itself if while I'm importing on both I try to look at a graph or summary or somthing.

I'm a former DBA in a previous life... although mostly Access and I know that was something that could cause corruption occasionally .

[kraada]

PT3 can't tell if someone else is importing into the database as far as I'm aware (there isn't any lock on the tables while importing), but importing to the same database from two different locations at one time would almost certainly cause corruption.

Now what you could do, though, is have each computer import into different databases and then for the HUD display from both of those databases on both virtual machines. That way whichever machine you're playing in, you'll have all of your data from both databases. Importing to the database and reading the same database elsewhere shouldn't cause problems, though, so you wouldn't have an issue seeing a graph while importing elsewhere.

[mjr161]

The hud isn't really my concern at all, it's just that I play different sites on different VM's. Will it make a difference if I'm not importing the same sites from each VM? I'm guessing it won't just checking.

So is networking the db really pretty much only for accessing it from multiple points? I would think at some point someone is bound to screw up and leave an auto import on at their desktop and start another up from a laptop from the porch while sipping ice tea on a hot summer day

[kraada]

It's entirely possible someone will do that, and I don't think it's absolutely certain that there will be database corruption, but I honestly don't know enough about the internal workings to say what cases work and what cases don't.

If you're playing on different sites on different VMs, the easiest thing is probably going to be just to have different databases for the different VMs and for your own hands just reimport played hands to one central database later. Selective export will be available in the next beta release so once you're up to date you can always just export the last week (or so) of data and reimport and that shouldn't take very long.

[mjr161]

Ok, I've been working on networking this all day and I just can't figure it out. I've followed the steps in the file linked above and edited the two .conf files.

However when I try to connect to the remote DB server from PT3 I get the following error....

"Unable to login to database (template1). Reason: FATAL: no pg_hba.conf entry for host "192.168.1.8", user "postgres", database "template1", SSL off"


Can you tell me what this means. I can tell that PT3 can see the db, and I've edited the .conf files so I'm really not sure what's going on.