PT3 performance tuning 2 HDDs

General discussion of PokerTracker 3.

Moderator: Moderators

Re: PT3 performance tuning 2 HDDs

Postby onthehustle » Sat Nov 29, 2008 12:11 am

kraada wrote:It sounds like you missed this step:

Click Start, click Run and type in "C:\Program Files\PokerTracker 3\Data\Schemas" and click ok. There is one file in here: schemas.postgre.sql. Right click on it, and click copy. Click Start, click Run type in D:\ and click ok. Right click in the window and click Paste to copy the schemas.postgre.sql to that location.

Alternately, you can just type:
Code: Select all
\i  C:\\Program Files\\PokerTracker 3\\Data\\Schemas\\schemas.postgres.sql


and that should do the exact same thing. Note all of the double backslashes.


The file is there but I still get the "no such" error.
onthehustle
 
Posts: 54
Joined: Sat Nov 15, 2008 6:52 pm

Re: PT3 performance tuning 2 HDDs

Postby WhiteRider » Sat Nov 29, 2008 5:13 am

Does the error message tell you what file doesn't exist? What is it?
I wonder if a space in the path you're entering is causing trouble. Try using quotes (I'm not sure this will work, but it's what you would do in DOS):
Code: Select all
\i  "C:\\Program Files\\PokerTracker 3\\Data\\Schemas\\schemas.postgres.sql"
WhiteRider
Moderator
 
Posts: 53972
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: PT3 performance tuning 2 HDDs

Postby brainslicer » Thu Dec 04, 2008 2:19 pm

when running \i schema.postgres.sql
a lot of errors show up...seems to work OK though. should i be concerned about it?

Code: Select all
INSERT 0 1
CREATE TABLE
psql:schema.postgres.sql:1379: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.lookup_hole_cards OWNER TO {postgresuser}...
                                                      ^
psql:schema.postgres.sql:1380: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "lookup_hole_cards_primary_key" for table "lookup_hole_cards"
ALTER TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
CREATE TABLE
psql:schema.postgres.sql:1571: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.lookup_positions OWNER TO {postgresuser};
                                                     ^
psql:schema.postgres.sql:1572: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "lookup_positions_primary_key" for table "lookup_positions"
ALTER TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
CREATE TABLE
psql:schema.postgres.sql:1643: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.lookup_sites OWNER TO {postgresuser};
                                                 ^
psql:schema.postgres.sql:1644: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "lookup_sites_primary_key" for table "lookup_sites"
ALTER TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
CREATE TABLE
psql:schema.postgres.sql:1666: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.lookup_actions OWNER TO {postgresuser};
                                                   ^
psql:schema.postgres.sql:1667: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "lookup_actions_primary_key" for table "lookup_actions"
ALTER TABLE
INSERT 0 1
CREATE TABLE
psql:schema.postgres.sql:1687: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.notes OWNER TO {postgresuser};
                                          ^
psql:schema.postgres.sql:1688: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "notes_primary_key" for table "notes"
ALTER TABLE
CREATE INDEX
CREATE TABLE
psql:schema.postgres.sql:1711: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.player OWNER TO {postgresuser};
                                           ^
psql:schema.postgres.sql:1712: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "player_primary_key" for table "player"
ALTER TABLE
CREATE INDEX
CREATE TABLE
psql:schema.postgres.sql:1730: ERROR:  syntax error at or near "{"
LINE 1: ALTER TABLE public.settings OWNER TO {postgresuser};
                                             ^
psql:schema.postgres.sql:1731: NOTICE:  ALTER TABLE / ADD PRIMARY KEY will creat
e implicit index "settings_primary_key" for table "settings"
ALTER TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
INSERT 0 1
pt3_newdb2=#
brainslicer
 
Posts: 30
Joined: Mon Nov 17, 2008 2:30 pm

Re: PT3 performance tuning 2 HDDs

Postby kraada » Thu Dec 04, 2008 2:25 pm

Those aren't errors they're just reports telling you what happened. That's normal and it looks like it got created fine.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: PT3 performance tuning 2 HDDs

Postby brainslicer » Thu Dec 04, 2008 3:58 pm

kraada wrote:Those aren't errors they're just reports telling you what happened. That's normal and it looks like it got created fine.

OK, thanks. One is easily to believe that a ton of "ERROR: syntax error at or near"-messages would mean something happened wrong :D
brainslicer
 
Posts: 30
Joined: Mon Nov 17, 2008 2:30 pm

Re: PT3 performance tuning 2 HDDs

Postby kraada » Thu Dec 04, 2008 4:03 pm

I missed those the first time through, but since you're logging in with the postgres user anyway the permissions should be set properly. Have you tried importing to the database yet?
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: PT3 performance tuning 2 HDDs

Postby brainslicer » Thu Dec 04, 2008 4:52 pm

kraada wrote:I missed those the first time through, but since you're logging in with the postgres user anyway the permissions should be set properly. Have you tried importing to the database yet?

Yes, seems to work ok...
brainslicer
 
Posts: 30
Joined: Mon Nov 17, 2008 2:30 pm

Re: PT3 performance tuning 2 HDDs

Postby kraada » Thu Dec 04, 2008 5:02 pm

Then you're definitely all set. Enjoy :)
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: PT3 performance tuning 2 HDDs

Postby bobbydavro » Thu Dec 11, 2008 6:53 pm

I'm trying to do this and I get no feedback in the postgres window at all.

I do CREATE Tablespace.....
and it gives no feedback

then
CREATE Database
no feedback

\connect pt3_newdb
no feedback

it seems to accept the commands but doesn't do anything or change the database.

The prompt just remains at
postgres'#

I've done all the copy the file and the permissions etc.

Any ideas?
bobbydavro
 
Posts: 42
Joined: Thu Feb 28, 2008 5:14 am

Re: PT3 performance tuning 2 HDDs

Postby kraada » Thu Dec 11, 2008 6:57 pm

PostgreSQL should be giving some feedback on the command line, though it doesn't give a ton. When a database is created it says: CREATE DATABASE. When you change databases the prompt should change.

Take a look in the most recent file located in C:\Program Files\PostgreSQL\8.3\data\pg_log and tell me what you see there.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

PreviousNext

Return to General [Read Only]

Who is online

Users browsing this forum: No registered users and 14 guests

cron