Re: Moving to postgresql and some ignorant questions - Mailing list pgsql-general

From Phoenix Kiula
Subject Re: Moving to postgresql and some ignorant questions
Date
Msg-id e373d31e0708141046t3cc114fcideb489bcbabb0f97@mail.gmail.com
Whole thread Raw
In response to Re: Moving to postgresql and some ignorant questions  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Moving to postgresql and some ignorant questions  (Bill Moran <wmoran@potentialtech.com>)
Re: Moving to postgresql and some ignorant questions  (Thomas Kellerer <spam_eater@gmx.net>)
Re: Moving to postgresql and some ignorant questions  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-general
> If you issue a BEGIN then nothing gets committed until you issue a COMMIT. If
> anything happens in the meantime then everything you've done since the BEGIN
> disappears.
>



There are some cases where I would like to bunch queries into a
transaction purely for speed purposes, but they're not interdependent
for integrity. E.g.,

  BEGIN TRANSACTION;
  UPDATE1;
  UPDATE2;
  UPDATE3;
  COMMIT;

If UPDATE2 fails because it, say, violates a foreign key constraint,
then so be it. I want UPDATE3 to go ahead. Is this not possible, or is
there an option I can use to do these kind of independent-query
transactions?

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Select time jump after adding filter; please help me figure out what I'm doing wrong.
Next
From: Bill Moran
Date:
Subject: Re: Moving to postgresql and some ignorant questions