* Merlin Moncure <mmoncure@gmail.com> [220811, 16:27]:
> 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]
> > ...
> > 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
Hi Merlin and thanks for your answer.
I have perused throughout the logs but was unable to find anything
strange. The sole remaining doubt is that the delimited text file used
to copy data to the table was itself corrupted.
AAMOF I've noticed in other occasion that sometimes, closing quickly a
file which was being edited with vim (from console) causes the latest
modification to fill up a whole line: the same might have occurred with
my original file, although I found strange that four (non consecutive)
out of 36 fields were involved. Moreover, supposing all the records
involved were coming from that possibly corrupted file, the supposed vim
corruption would have taken effect 'vertically' for the four fields
concerned, which would be a completely new experience to me...
Regards, ennio
--
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?//
Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ] (°|°)
Ricevo solo messaggi Content-Type: plain/text (no html o multipart). )=(
!!! --> e-mail a mio nome via OE (M$) sono false e infette <-- !!!
