Re: Data corruption after an update set ...?
От | Merlin Moncure |
---|---|
Тема | Re: Data corruption after an update set ...? |
Дата | |
Msg-id | CAHyXU0w17Vg_4rMqsbkZ=aZyN4x1UK7vjS_QLch-Pc-TTB_w-w@mail.gmail.com обсуждение исходный текст |
Ответ на | Data corruption after an update set ...? (Ennio-Sr <nasr.laili@tin.it>) |
Ответы |
Re: Data corruption after an update set ...?
|
Список | pgsql-novice |
On Mon, Aug 22, 2011 at 3:36 PM, Ennio-Sr <nasr.laili@tin.it> wrote: > [Using postgresql-8.4.8-0squeeze1 under GNU-linux/debian] > > > Hi all! > > I've just discovered that 456 records out of 1510 contained in a table > of my db bear the same content in two fields: the original data have > disappeared and I do not know how this occurred. > > Luckily enough I'll be able to recover a large part of lost data but > would like to understand what happened: looking at .psql_history I can > see the command which might have caused the whole mess (see below) > although similar commands have been used in many other occasions without > doing any harm. > > So the question are: > 1. what caused the mess? > 2. might depend on the processor (1300Mhz 10 years old)? nope > 3. a HD failure? nope My money is on 'operator error'. Without having access to the logs and queries in question, that's what I have to assume. As always, frequent backups are your best defense. merlin
В списке pgsql-novice по дате отправления: