Hello All,
I have been attempting to move our database to our new database
server
but i have encountered a few problems along the way. One of the
errors
that I encountered was the error below when trying to drop a table so
I
could re-build it.
ERROR: cache lookup failed for relation 411727
Never having seen this error I turned to Google to try and determine
what
the problem is and found this entry from our previous Web Dev/DBA
about
a slony issue. Unfortunatly for us he has moved on to better things
which
means i can't quiz him on what happened and what he done to resolve
it
if he indeed was able to. Having read through the thread it seems to
be
the same or a similar issue
http://www.thescripts.com/forum/thread423390.html
I need to be able to determine whats causing this, This will be the
second
time the Database has moved since and while the errors mentioned in
the
above thread where on a test Database we did have slony ver 1 running
on our live database and I am wondering if this could be responsible
for
the errors esspecially as after the last DBA left company no one
appears
to know what happened with slony (I started as he left there was
nothing
in the handover as I'd never seen postgres before).
So basically I need to find a way to figure out what the errors are
and find
a way to resolve them, I only noticed this when testing and over night
build
of our database tables and one that usually takes 35 mins took 2
hours
10 minutes which was unacceptable.
DB: PostgreSQL 8.1.9
OS: Red Hat Enterprise 5
Thanks In advance
David Phillips
Cromwell Tools Ltd
Leicester