In response to Victor Hugo dos Santos <listas....@gmail.com>:

> 
> > The other error is indicative of a filesystem problem.  I can't think
> > of any normal circumstance that would cause that error, and thus it
> > concerns me.
> 
> mmm.. the RAID controller, badblocks and fsck don't show any errors in
> the filesystem/disks !! :-(
> 
> 
> > You can find out what table/view/whatever is the problem by doing:
> > SELECT * FROM pg_class WHERE oid = 2247622656;
> 
> this is the output:
> 
> ====================
> relname | relnamespace | reltype | relowner | relam | relfilenode |
> reltablespace | relpages | reltuples | reltoastrelid | reltoastidxid |
> relhasindex | relisshared | relistemp | relkind | relnatts | relchecks
> | relhasoids | relhaspkey | relhasrules | relhastriggers |
> relhassubclass | relfrozenxid | relacl | reloptions
> ---------+--------------+---------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+-------------+-------------+-----------+---------+----------+-----------+------------+------------+-------------+----------------+----------------+--------------+--------+------------
> (0 rows)
> 
> (END)
> ====================
> 
> many thanks.

Well, it's gone alright.

Here's my recommendation:
0) Make sure you're getting reliable backups of the database.  Try
   restoring one to another system.
1) make sure you're running the latest version of PostgreSQL on the
   major branch you're on.  i.e. if you're running 8.2.11, upgrade
   to 8.2.13
2) If the error is happening frequently, restart PostgreSQL and see
   if it goes away.  There have been some issues with name -> oid
   caching when relations are dropped and recreated with the same
   name while another connection is caching that mapping.
3) If the problem is still happening.  Get a backup, delete your
   pg_data directory, re-init the database and restore from
   backup.
4) If the problem is still happening after that, go to the PostgreSQL
   community and ask for help.  I agree with Kern that this probably
   isn't a Bacula problem.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmo...@collaborativefusion.com
Phone: 412-422-3463x4023

****************************************************************
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to