From: | Marcelo Sena <marceloslacerda(at)gmail(dot)com> |
---|---|
To: | |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Behaviour of sql language function |
Date: | 2012-04-27 11:48:29 |
Message-ID: | CAPmRTtMtNFeGEMewhntOyf3GPt=O=OU+N1ZZcj7hW9Qem5E7aA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Oh, nice, I haven't noticed that fact. Thanks!
--
Marcelo Lacerda
On Thu, Apr 26, 2012 at 5:53 PM, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov
> wrote:
> Marcelo Sena <marceloslacerda(at)gmail(dot)com> wrote:
>
> > So, is it documented somewhere?
>
> http://www.postgresql.org/docs/current/static/tutorial-transactions.html
>
> | PostgreSQL actually treats every SQL statement as being executed
> | within a transaction. If you do not issue a BEGIN command, then
> | each individual statement has an implicit BEGIN and (if
> | successful) COMMIT wrapped around it.
>
> Combine this with the fact that a function can only run in the
> context of a command, like:
>
> SELECT func_name();
>
> You have your guarantee -- as long as you understand the possible
> action of subtransactions (like savepoints).
>
> -Kevin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-04-28 21:24:36 | Documentation of underlying functions for statistics views |
Previous Message | Selena Deckelmann | 2012-04-27 00:46:49 | Re: "TL;DR:" |