Unable to create PostgreSQL database: PT3 Alpha....

[APerfect10]

[quote="_dave_"5p2][quote="Chaser8"5p2]http://img204.imageshack.us/my.php?image=postgresqo6.png

This?[/quote5p2]
That looks like HM...

Unless you are certain what you are doing, changing the superuser name to not "postgres" is a recepie for disaster imo.[/quote5p2]

What are you trying to do? Connect PostgreSQL to PT2? That is the correct configuration window for PostgreSQL in PT2.

As dave stated, make sure that your username is the same one that you entered. By default it is "postgres" which you may have changed.

Best regards,

Derek

[Chaser8]

[quote="APerfect10"qi0][quote="_dave_"qi0][quote="Chaser8"qi0]http://img204.imageshack.us/my.php?image=postgresqo6.png

This?[/quoteqi0]
That looks like HM...

Unless you are certain what you are doing, changing the superuser name to not "postgres" is a recepie for disaster imo.[/quoteqi0]

What are you trying to do? Connect PostgreSQL to PT2? That is the correct configuration window for PostgreSQL in PT2.

As dave stated, make sure that your username is the same one that you entered. By default it is "postgres" which you may have changed.

Best regards,

Derek[/quoteqi0]

I'm trying to create a db in PokerTracker3. I have made absolutely sure that my username and password are correct. What could be the problem?

[APerfect10]

[quote="chaser8"q9q]I'm trying to create a db in PokerTracker3. I have made absolutely sure that my username and password are correct. What could be the problem?[/quoteq9q]

Go Start->Program Files->PostgreSQL 8.2->Configuration Files->Edit pg_hba.conf

At the bottom of the file change the method from "md5" to "trust". Restart your computer and it should work.

Best regards,

Derek

[Chaser8]

I changed both md5 values to trust and I still got the same message: Unable to create PostgreSQL database: PT3 Alpha DB1
Reason: Unable to execute query: CREATE DATABASE "PT3 Alpha DB1" WITH OWNER = Chaser ENCODING = 'SQL_ASCII' TABLESPACE = pg_default;; Reason: Fatal Error (ERROR: role "chaser" does not exist )

I just reinstalled windows xp last week. Everything is fresh (pt2, pahud, postgre). What could be different in my system from the others'? Is there a file in postgre that I can send you that contains my information?

Here's what I see in pgAdmin III
http://img132.imageshack.us/my.php?imag ... ngsjy8.jpg

[Josh]

Try using postgres instead of Chaser now.

[Chaser8]

I tried postgres with and without a password. and it didn't work.

Here's what I see in pgadmin III
http://img132.imageshack.us/my.php?imag ... ngsjy8.jpg

[Josh]

In pgAdmin, right-click a database name and select "Backup". Select "PLAIN", and check "Only schema" and "Create DB". Hit OK, open the file you backed up to, then copy starting at the "CREATE DATABASE" statement and ending at the first "CREATE TABLE" statement. Paste what you copied here.

[Chaser8]

pg_dump: creating DATABASE CHASER
pg_dump: connecting to new database "CHASER"
pg_dump: creating SCHEMA public
pg_dump: creating COMMENT SCHEMA public
pg_dump: creating PROCEDURAL LANGUAGE plpgsql

[Josh]

What file did you dump to? This looks like the results of dump command, not the dump itself.

[Chaser8]

[bm0u]First of all, after I load up pgadmin, and "connect" to postgresql database server, I see that my chaser database has a big red X on the icon. When I click the chaser database, I get this msg:[/bm0u]

Database encoding
The database CHASER is created to store data using the SQL_ASCII encoding. This encoding is defined for 7 bit characters only; the meaning of characters with the 8th bit set (non-ASCII characters 127-255) is not defined. Consequently, it is not possible for the server to convert the data to other encodings.
If you're storing non-ASCII data in the database, you're strongly encouraged to use a proper database encoding representing your locale character set to take benefit from the automatic conversion to different client encodings when needed. If you store non-ASCII data in an SQL_ASCII database, you may encounter weird characters written to or read from the database, caused by code conversion problems. This may cause you a lot of headache when accessing the database using different client programs and drivers.
For most installations, Unicode (UTF8) encoding will provide the most flexible capabilities.
[bm0u]
and now this is what I get in the backup:[/bm0u]

CREATE DATABASE "CHASER" WITH TEMPLATE = template0 ENCODING = 'SQL_ASCII';


ALTER DATABASE "CHASER" OWNER TO "Chaser";

\connect "CHASER"

SET client_encoding = 'SQL_ASCII';
SET standard_conforming_strings = off;
SET check_function_bodies = false;
SET client_min_messages = warning;
SET escape_string_warning = off;

--
-- TOC entry 1733 (class 0 OID 0)
-- Dependencies: 4
-- Name: SCHEMA public; Type: COMMENT; Schema: -; Owner: Chaser
--

COMMENT ON SCHEMA public IS 'Standard public schema';


--
-- TOC entry 301 (class 2612 OID 16386)
-- Name: plpgsql; Type: PROCEDURAL LANGUAGE; Schema: -; Owner: Chaser
--

CREATE PROCEDURAL LANGUAGE plpgsql;


SET search_path = public, pg_catalog;

SET default_tablespace = '';

SET default_with_oids = false;

--
-- TOC entry 1307 (class 1259 OID 16409)
-- Dependencies: 4
-- Name: blind_structure; Type: TABLE; Schema: public; Owner: Chaser; Tablespace:
--

CREATE TABLE blind_structure (
blind_structure_id smallint,
blind_structure_desc text,
big_bet integer
);