> > 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
> > ;-)
> >
>
> nah .. ext3 and no crashes
Interesting. Because it really sounds like your filesystem just dropped
a file, which normally
>
> 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
> ;-)
>
nah .. ext3 and no crashes
> Also, what version of pg is this? Is it a large/old database, and if so
> are you vacuum:ing regularly?
>
> > 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
>
> 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 ..
> my postgresql-log got errors about a missing table ( and an
> index on it) now the wired thing is that table is not defined
> in the create script at all (checked with CVS)
>
> wtf is wrong here ?
Nothing. Bacula forcibly deletes these these objects even if they don't
exist, to make sure they
my postgresql-log got errors about a missing table ( and an index on it)
now the wired thing is that table is not defined in the create script at
all (checked with CVS)
wtf is wrong here ?
it's working like that but i can't backup database since postgresql is
complaining about missing transactio
