updating new postgres version and pt3 didnt work

[emenius]

since i update to the newest version 8got no hud at ruh and this should help) i cant use pt3



i make it short: im a 100% pc noob
most of which you will tell me i will not understand
but: is there at least any chance that i can save my hud which i build in endless hoursß

[kraada]

Your HUD should be fine - why did you upgrade PostgreSQL? From the error it sounds like PostgreSQL is not running at all successfully at the moment.

[emenius]

but how can i get my hud when i cant open pt3?

i updated postgre because i didnt gat a hud at rushpoker. and i read the updating to the newest version could fix this

[WhiteRider]

What Kraada means is that updating PT3 or PostgreSQL does not affect the file that stores your HUD, so once we get PostgreSQL working again everything should be fine.

What version of PostgreSQL did you have before you updated, and what did you update to?

Click Start, type services.msc and hit enter. Do you see PostgreSQL on the list of services to start? If so, can you start it?

[emenius]

it stands on automatic and starting it produces failur 1053

it was version 8.x (i did let it install via pt3) and is now 9.0.1

[WhiteRider]

Did you backup your database before you updated and restore it afterwards?
PostgreSQL 9.x cannot read 8.x databases.

The easiest solution will probably be to uninstall 9.x and reinstall your previous version, then PT3 will be able to reconnect to it and the existing databases (as long as you didn't delete them).

[emenius]

i uninstall all sql datas from my pc and install 9.0.1 new. no wit works.
but still no hud in rush, except one at the wrong place 8and the whole time the same player)

[kraada]

When you start with a new database it takes a while to see any data in Rush because when the players at the table have no data in the database, you don't see any boxes for them.

[emenius]

but this cant be the problem why this one hud i have is always on the same playce always from one player during my last 1,2k hand session

[kraada]

Then please restart PT3 using the Logging Enabled link, reproduce and report this problem and we'll investigate further for you.