> > No, postgresql transaction log errors have nothing to do > with what's > > in your database. What exactly is the error you get about the logs? > > > > //Magnus > > i'm getting errors when trying to do a pg_dump of my catalog > database ... > > i already deleted and re-created the database but to no avail ... > > any ideas ?
Yikes. You have corrupt files on disk. Have you had hardware problem or OS crashes lately? Or running some funky beta-version of a filesystem ;-) Also, what version of pg is this? Is it a large/old database, and if so are you vacuum:ing regularly? > i thought the reason could be bacula having errors... Nope, not related. Anyway. The proper fix is to restore a backup from before the disk corruption occured. If you can't do this, try to recreate the file using: dd if=/dev/zero bs=1k count=128 of=/var/lib/postgres/data/pg_clog/0000 This only applies if the file does not exist, of course - if it does, and pg for some reason can't see it, you have a different problem. *WARNING* This may quite well lose data for you, because it will zero out the visibility info. If it works, pg_dump yuor database right away, re-initdb, and reload that backup. You'll definitly want to do an extra round of fsck on your filesystem, probably with badblocks checking enabled. //Magnus _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
