Postgres compression error

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

Postgres compression error

Postby pkru » Wed May 21, 2008 5:42 pm

When compressing database I get the following error:

7 - SQLSTATE = 23505
ERROR: duplicate key violates unique constraint
"pg_statistic_relid_att_index"
Error while executing query

How do I fix this so i can complete compression?
pkru
 
Posts: 9
Joined: Wed May 21, 2008 3:39 pm

Re: Postgres compression error

Postby prajna » Wed May 21, 2008 6:17 pm

You asked this here and its also been answered.

~ Thomas
[Pokertracker support]
prajna
 
Posts: 734
Joined: Thu Apr 03, 2008 1:58 pm

Re: Postgres compression error

Postby ptrack pat » Wed May 21, 2008 7:13 pm

Is this with PT2 or PT3 you get this error?
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: Postgres compression error

Postby pkru » Thu May 22, 2008 5:55 pm

i apologize, posted to PT3 forum by accident. So what do u need me to do to get this fixed for PT2?
pkru
 
Posts: 9
Joined: Wed May 21, 2008 3:39 pm

Re: Postgres compression error

Postby ptrack pat » Thu May 22, 2008 7:03 pm

I've never seen this error before, I don't know how to correct it. When did you last do a backup before you started getting this?

Do the hands import without error?
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: Postgres compression error

Postby pkru » Fri May 23, 2008 1:26 pm

hands still import, using bodog hand grabber, backup lol yeah right (doh). should i just export the hands to a file and then reimport to a fresh database?
pkru
 
Posts: 9
Joined: Wed May 21, 2008 3:39 pm

Re: Postgres compression error

Postby ptrack pat » Fri May 23, 2008 1:33 pm

should i just export the hands to a file and then reimport to a fresh database?


Yes, I would try this.

This table name giving the, pg_statistic_relid_att_index, is not a PT database table so it must be a system table. Therefore it appears something in your db is corrupted. So I would suggest starting a fresh db, convert that to PostgreSQL and then import just a few hands into the new PostgreSQL db and then try to do the vacuum/analyze and see if it works. If you don't get this same error again then continue to import the rest of the hands.
ptrack pat
 
Posts: 4841
Joined: Sun Dec 09, 2007 12:38 pm

Re: Postgres compression error

Postby pkru » Thu May 29, 2008 10:13 pm

yeah that worked thanks.
pkru
 
Posts: 9
Joined: Wed May 21, 2008 3:39 pm


Return to PostgreSQL Forum

Who is online

Users browsing this forum: No registered users and 0 guests