postgre/database errors for too long

[djfl]

Hi. Too many errors for too long. the pto guys asked me to post my latest post here.

hope you can help.




viewtopic.php?f=34&t=16737&p=79420#p79420

[ptrack pat]

So can you explain to me in a nutshell what the problem still is? Are you still getting this error...

"SQL Connection exception: Failed to connect to datasource: FATAL: password authentication failed for user 'postgres'"

When you try to use PTO? If so, and you have already changed your PostgreSQL Settings window to be using the newest, correct values then open the File > Maintain Database Names window.
Click the Add button.
Enter a description, check the "Dflt" box and in the last field choose "Select existing PostgreSQL database" from the list.
Select your PTO database from the window that opens, click OK to save all changes.
Now CLOSE AND REOPEN PTO and see what it does.

[djfl]

I'll try to list the main details in order in point form

-I have a laptop and a desktop computer both using postgresql databases. I play on each, make backups, and transfer them from computer to computer as required. A few months ago, the backup from my laptop only created errors on the desktop. I made 5 backups and they all failed. Posted on the pto page and we couldn't figure out the problem.
-I ended up doing an uninstall/reinstall of pto and postgre on the desktop computer...without removing programfiles/postgre folder. I'm now hating myself for this.
-While reinstalling postgre, my initial login info "postgres for the login, password for the password" stopped working. I got the same error msg that was posted in one of the old postgre help posts. Either way, I created a new postgre login "postgres1" with the same password. That worked fine.
-I exported to file the laptop database and made a new database on the desktop that seemed to work fine.
-I've noticed now that on startup, pto and pahud both give me the same SQL exception error you mentioned in your reply

As for my settings in pto, the login name is postgres1. There is no reference in pto about the old postgres login. However, I think that info may still be in the postgres folder somewhere that I can't find...and I have looked.
The proper database is the dflt, etc etc. And I've closed and reopened pto too many times.
I have several other software errors as well, but this one is the biggest and I really wanna get it dealt with first.


The more I describe this, the more it sounds like I should do another un/reinstall of postgres...following the uninstall instructions on the pokertracker walkthrough this time.
If you think I should, please give me the link to follow to uninstall and to reinstall just to make sure I do it right.

Other than that, any ideas...and will I have to do any un/reinstalling or changing of database info in pto if I do do the postgre un/reinstall?

Thanks again.

[ptrack pat]

As for my settings in pto, the login name is postgres1. There is no reference in pto about the old postgres login. However, I think that info may still be in the postgres folder somewhere that I can't find...and I have looked.

This is why I told you above to create a new database entry. Did you try that? All of the registry settings for the previously defined databases are still pointing to "postgres" as the user name. If you have changed the PostgreSQL Settings window to use the new user name then adding a brand new entry on the File > Maintain Database Names window (selecting the existing PostgreSQL database from the list) might work because it will then create new registry entries with the "postgres1" name for that database.

[djfl]

I think that did it Pat. I don't know why, since my previous database was also a new entry with the postgres1 login, but I'll definitely take the fix.

I still got the error w PAHUD, so what I did was delete the other 3 databases that PTO had. I'm still getting the error message, but I believe that's because PAHUD is seeing my PTH databases...for which I've done no in/reinstall or changing postgres to postgres1. I'll get that figured out eventually and let you know if I have any problems from there.

Either way, thanks again.

[ptrack pat]

Try going to the PokerAce database config settings window...
http://www.pokertracker.com/products/PA ... gprefdbase

And setting it up so just your NEW PTO database entry is selected from the list. See if that stops the errors from PAHUD.

[djfl]

Well the PTO error is back again. I can't access the database. The error I get on startup is
"Unable to connect to the database
101-SQLState = 08001
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request"



Ideas? I haven't made any changes to the databases or anything else since it started up fine. I'm starting to think I may need an old priest and a young priest...

[ptrack pat]

That's a different error altogether. Try restarting the computer and trying it again.