Hello,
Thanks for all your answers!
I discovered the table that was causing the error, delete it and
create it again (I miss some data but at least everything else is
working now)
Yes, for the backup we copy everything we had under /data (the
directory containing "base", "global", and so on ... we do backups
every day from the server), and then we restore the whole /data
directory at once ... but it did not solve the problem ..
What do you mean by we can't simply take a filesystem copy of a
running database? :-O ... How should we then do the backups (so next
time I will not have the same problem again) ?
Millions of thanks again!
Vanessa
On 10 Jul 2009, at 04:06, decibel wrote:
> On Jul 4, 2009, at 8:06 AM, Craig Ringer wrote:
>> On Fri, 2009-07-03 at 15:00 +0100, Vanessa Lopez wrote:
>>> I don't know much about postgre, I have no clue what else I can do.
>>> Please, please any help is very very much appreciated I have lots of
>>> databases and months of work in postgre (also lots of backups for
>>> the
>>> data in /data)
>>
>> When you say "in /data", do you mean the directory that contains the
>> directories "pg_xlog", "base", "global", "pg_clog", etc ?
>>
>> Did you back up and restore the WHOLE data directory at once? Or
>> did you
>> restore only parts of it?
>
>
> And how exactly did you make the backups? You can't simply take a
> filesystem copy of a running database; that won't work.
> --
> Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org
> Give your computer some brain candy! www.distributed.net Team #1828
>
>