FATAL: database PTPGSQL2 does not exist

Forum with tips, support, etc, on using the PostgreSQL database with Poker Tracker. Please post any PostgreSQL questions here.

Re: FATAL: database PTPGSQL2 does not exist

Postby brianbrianbrian » Wed May 07, 2008 4:09 pm

it is started

postgreSQL datab.. postgreSQL d. started automa. .\postgres
brianbrianbrian
 
Posts: 15
Joined: Tue May 06, 2008 8:20 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby ptrack pat » Wed May 07, 2008 4:27 pm

The service is running but you can't login to pgAdmin without getting the database error, that's what is happening? I don't understand why that would be happening.

Try going to the Start > Programs > PostgreSQL 8.x > Configuration Files > Edit pg_hba.conf

Go to the bottom of the file and there should be 2 entries that look like this:

====
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
#host all all ::1/128 md5
====

Is this what your file looks like?
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby brianbrianbrian » Wed May 07, 2008 4:39 pm

no
it is

# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5

shall i change it?
brianbrianbrian
 
Posts: 15
Joined: Tue May 06, 2008 8:20 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby ptrack pat » Wed May 07, 2008 4:41 pm

You could try, I don't know if it will help.
After you edit/save the file, try restarting the computer too.
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby brianbrianbrian » Wed May 07, 2008 4:47 pm

no it doesnt help :(
brianbrianbrian
 
Posts: 15
Joined: Tue May 06, 2008 8:20 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby ptrack pat » Wed May 07, 2008 4:51 pm

You are getting the db error when you try to login through pgAdmin, right?

I assume you also get an error like this when you try to open PT...instead of the "database not found" error you were getting before?
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby brianbrianbrian » Wed May 07, 2008 4:55 pm

Pokertracker works fine now
I ve just problems when I use PGAdmin and
when I use Spadeeye and Eyepoker, which scans the tables of the pokersoftware. the same error appears
brianbrianbrian
 
Posts: 15
Joined: Tue May 06, 2008 8:20 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby ptrack pat » Wed May 07, 2008 4:57 pm

That really doesn't make sense because I don't know how PT would run but those other programs do not. Are you sure your default database is this PostgreSQL db and not the Access database?
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby brianbrianbrian » Wed May 07, 2008 5:04 pm

OPEN--------------------NAme---------------------------------DFLT ---------------type-----------port # ---------------------------- DB/file/dbname
No-----------------------my first poker tracker database----- ------------- access--------------------------------D:\Pokertracker2\ptrack2.mdb
Yes----------------------Partypoker------------------------------ x -------------PostgreSQL-------5432 ------------------------PTPGSQL2
brianbrianbrian
 
Posts: 15
Joined: Tue May 06, 2008 8:20 pm

Re: FATAL: database PTPGSQL2 does not exist

Postby brianbrianbrian » Wed May 07, 2008 5:13 pm

the whole error:


Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5432?
If you encounter this message, please check if the server you're trying to contact is actually running PostgreSQL on the given port. Test if you have network connectivity from your client to the server host using ping or equivalent tools. Is your network / VPN / SSH tunnel / firewall configured correctly?
For security reasons, PostgreSQL does not listen on all available IP addresses on the server machine initially. In order to access the server over the network, you need to enable listening on the address first.
For PostgreSQL servers starting with version 8.0, this is controlled using the "listen_addresses" parameter in the postgresql.conf file. Here, you can enter a list of IP addresses the server should listen on, or simply use '*' to listen on all available IP addresses. For earlier servers (Version 7.3 or 7.4), you'll need to set the "tcpip_socket" parameter to 'true'.
You can use the postgresql.conf editor that is built into pgAdmin III to edit the postgresql.conf configuration file. After changing this file, you need to restart the server process to make the setting effective.
If you double-checked your configuration but still get this error message, it's still unlikely that you encounter a fatal PostgreSQL misbehaviour. You probably have some low level network connectivity problems (e.g. firewall configuration). Please check this thoroughly before reporting a bug to the PostgreSQL community.
brianbrianbrian
 
Posts: 15
Joined: Tue May 06, 2008 8:20 pm

PreviousNext

Return to PostgreSQL Forum

Who is online

Users browsing this forum: No registered users and 1 guest