Re: [SQL] ERROR: failed to re-find parent key in pk_ep07

2007-10-25 Thread Otniel Michael


Note: forwarded message attached.

-- 
 He who is quick to become angry will commit folly, and a crafty man is hated 
 

 __
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com ---BeginMessage---
OC. I will try to upgrade the postgres. What version that can fix this problem? 
Postgres 8.2.5? Postgres 8.1?

Now, i use postgres 8.0.3, what effect when i upgrade the postgres version?
I heared that i should check my sql? In postgres 8.0.3 show as warning, in 
postgres 8.1 as error?

Thanks.

Tom Lane [EMAIL PROTECTED] wrote: Otniel Michael  writes:
 When i was vacuum the database, the vacuum if failed. And I get this error. 
 Any ideas an to fix this?
ERROR:  failed to re-find parent key in pk_ep07

Update to a newer PG version, possibly?  This symptom has been seen
before...

   regards, tom lane



-- 
 He who is quick to become angry will commit folly, and a crafty man is hated 
 

 __
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com ---End Message---

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [SQL] ERROR: failed to re-find parent key in pk_ep07

2007-10-25 Thread Gregory Stark
Tom Lane [EMAIL PROTECTED] writes:

 Otniel Michael [EMAIL PROTECTED] writes:
 When i was vacuum the database, the vacuum if failed. And I get this error. 
 Any ideas an to fix this?
ERROR:  failed to re-find parent key in pk_ep07

 Update to a newer PG version, possibly?  This symptom has been seen
 before...

It was fixed in these bug-fix releases: 7.4.15, 8.0.10, and 8.1.6 which were
released on August 1st of this year. There have actually been 3 to 4 more
bug-fix releases since those too.

-- 
  Gregory Stark
  EnterpriseDB  http://www.enterprisedb.com

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


Re: [SQL] ERROR: failed to re-find parent key in pk_ep07

2007-10-25 Thread Filip RembiaƂkowski
2007/10/25, Otniel Michael [EMAIL PROTECTED]:
 OC. I will try to upgrade the postgres. What version that can fix this
 problem? Postgres 8.2.5? Postgres 8.1?

 Now, i use postgres 8.0.3, what effect when i upgrade the postgres version?
 I heared that i should check my sql? In postgres 8.0.3 show as warning, in
 postgres 8.1 as error?


If you can afford some testing time, try with the very latest stable
version (8.2.5 at the moment).

If you can't, just take the last patchlevel from 8.0.x series  - the
upgrade is seamless
(just backup - stop the server - replace binaries - start servar )

Detrailed upgrade procedures are described either in manual or
somewhere on the net.


cheers

-- 
Filip RembiaƂkowski

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


[SQL] ERROR: failed to re-find parent key in pk_ep07

2007-10-24 Thread Otniel Michael
When i was vacuum the database, the vacuum if failed. And I get this error. Any 
ideas an to fix this?

   ERROR:  failed to re-find parent key in pk_ep07

Thanks before.

Note : EP07 is name of tables.


-- 
 He who is quick to become angry will commit folly, and a crafty man is hated 
 

 __
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [SQL] ERROR: failed to re-find parent key in pk_ep07

2007-10-24 Thread Tom Lane
Otniel Michael [EMAIL PROTECTED] writes:
 When i was vacuum the database, the vacuum if failed. And I get this error. 
 Any ideas an to fix this?
ERROR:  failed to re-find parent key in pk_ep07

Update to a newer PG version, possibly?  This symptom has been seen
before...

regards, tom lane

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match