Re: TRANSACTION FOR AN UPDATE COMMAND WITH ONE TABLE

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: TRANSACTION FOR AN UPDATE COMMAND WITH ONE TABLE
Date: 2010-04-08 09:48:04
Message-ID: hpk8ok$dsf$4@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On 2010-04-06, JORGE MALDONADO <jorgemal1960(at)gmail(dot)com> wrote:
> --001485e609d13a8c510483958cf7
> Content-Type: text/plain; charset=ISO-8859-1
>
> I have an UPDATE command which modifies several records of one (only one)
> table.
> Is it feasible (or a good idea) to include it in a transaction block to make
> sure the process is performed with integrity?
> Or
> Does PostgreSQL has some kind of auto-integrity check with simple DB
> operations like?

a single update command either succeeds or fails.
if it fails no records will have changed, if it succeds all the
matching records will have been updated.

wrapping it in a transaction will gain you nothing.

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Machiel Richards 2010-04-08 12:52:37 FW: Postgres cpu & memory usage
Previous Message Jasen Betts 2010-04-08 09:42:36 Re: Read only postgres server