Re: Questions regarding interaction of stored functions and transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Questions regarding interaction of stored functions and transactions
Date: 2005-03-24 15:12:20
Message-ID: 26733.1111677140@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> Let's take the following fictional scenerio:

> BEGIN;
> INSERT INTO table1 VALUES ('somestring');
> INSERT INTO table1 VALUES ('anotherstring');
> SELECT user_defined_function();
> COMMIT;

> In this case, user_defined_function() does a lot more table manipulation.
> I don't want that to be done if any statement prior fails, but it seems as
> if it's always done, regardless. It seems as if the second INSERT is not
> executed if the first fails, but the function is always called.

Sorry, I don't believe a word of that. If the first insert fails,
everything will be rejected until COMMIT.

Possibly you need to show a less fictionalized version of your problem.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Treat 2005-03-24 15:13:58 Re: Good Books
Previous Message Tom Lane 2005-03-24 15:10:14 Re: Good Books