Skip site navigation (1) Skip section navigation (2)

Re: Disruptive corruption of data during an update

From: Ennio-Sr <nasr(dot)laili(at)tin(dot)it>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: Disruptive corruption of data during an update
Date: 2012-03-29 16:00:13
Message-ID: 20120329160013.GA29605@deby.ei.hnet (view raw or flat)
Thread:
Lists: pgsql-novice
* Steve T <steve(at)retsol(dot)co(dot)uk> [290312, 13:40]:
> On Thu, 2012-03-29 at 13:49 +0200, Ennio-Sr wrote:
> 
> 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=# begin;
> BEGIN
> dev_reinsure=# update address set addrLine1='N where recno=2';
> UPDATE 911
> dev_reinsure=# rollback;
> ROLLBACK
> 

Thank you Steve, this seems to be a good practice which I must get
accustomed to use!
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 <-- !!!

In response to

pgsql-novice by date

Next:From: Alan HodgsonDate: 2012-03-29 17:25:53
Subject: Re: Disruptive corruption of data during an update
Previous:From: ennioDate: 2012-03-29 14:04:26
Subject: Re: Disruptive corruption of data during an update

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group