On Thu, 2012-03-29 at 13:49 +0200, Ennio-Sr wrote:
> A few minutes ago I wrote:
> ---- quote
> update command:
> mydb=> update bibl set argomento='curatori', autore='DELLA VOLPE Galvano \
> (con due capitoli aggiunti e note di) where n_prog=3285;
> mydb'> ';
> UPDATE 12845
> Having an adequate back-up I think I'll be able to recover the data, but
> can someone explain what the hell happened?
> -------- unquote
> Having come out of the initial panic I reconsidered the thing with calm
> and of course 'discovered' that the program has done exactly what I told
> it to do, as the 'where' clause was incorporated within the two «'».
> My question now is:
> is there any possibility to recover such type of error while postgres is
> still running and no other transacion has been committed?
I cannot help with the recovery, but as a general rule I tend to place
all updates/deletes within an explicit transaction. Obviously you can
then rollback the transaction should the results not be as required.
dev_reinsure=# update address set addrLine1='N where recno=2';
> [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 <-- !!!
DDI: 01323 488548
In response to
pgsql-novice by date
|Next:||From: ennio||Date: 2012-03-29 14:04:26|
|Subject: Re: Disruptive corruption of data during an update|
|Previous:||From: Ennio-Sr||Date: 2012-03-29 11:49:01|
|Subject: Disruptive corruption of data during an update|