| From: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Moving to postgresql and some ignorant questions |
| Date: | 2007-08-14 17:46:34 |
| Message-ID: | e373d31e0708141046t3cc114fcideb489bcbabb0f97@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2007-08-14 17:56:51 | Re: Moving to postgresql and some ignorant questions |
| Previous Message | Richard Huxton | 2007-08-14 17:41:29 | Re: Select time jump after adding filter; please help me figure out what I'm doing wrong. |