From: | Alexander Kotelnikov <sacha(at)myxomop(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Transaction blocks |
Date: | 2005-08-11 12:03:45 |
Message-ID: | 87k6is8yu6.fsf@myxomop.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
>>>>> On Wed, 10 Aug 2005 18:25:57 -0600
>>>>> "MF" == Michael Fuhr <mike(at)fuhr(dot)org> wrote:
MF>
MF> On Wed, Aug 10, 2005 at 07:13:23PM +0400, Alexander Kotelnikov wrote:
>> I believe, any procedure language function is a transaction block, and
>> I think, I even read this somewere in docs, but can not find where
>> now, so, is it true, for all languages (SQL, PL/pgsql, perl etc)?
MF>
MF> This might be what you read:
MF>
MF> http://www.postgresql.org/docs/8.0/static/plpgsql-structure.html
MF>
MF> "Functions and trigger procedures are always executed within a
MF> transaction established by an outer query -- they cannot start or
MF> commit that transaction, since there would be no context for them
MF> to execute in."
Oops, I missed this, thanks. But what about PL's other than pgsql?
--
Alexander Kotelnikov
Saint-Petersburg, Russia
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Davis | 2005-08-11 12:26:02 | Index choice |
Previous Message | Alexander Kotelnikov | 2005-08-11 10:50:11 | passing column name to a PL/pgsql function for ALTER TABLE ADD |