Re: Behaviour of sql language function - Mailing list pgsql-docs

From Marcelo Sena
Subject Re: Behaviour of sql language function
Date
Msg-id CAPmRTtMtNFeGEMewhntOyf3GPt=O=OU+N1ZZcj7hW9Qem5E7aA@mail.gmail.com
Whole thread Raw
In response to Re: Behaviour of sql language function  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List 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.Grittner@wicourts.gov> wrote:
Marcelo Sena <marceloslacerda@gmail.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

pgsql-docs by date:

Previous
From: Selena Deckelmann
Date:
Subject: Re: "TL;DR:"
Next
From: Tom Lane
Date:
Subject: Documentation of underlying functions for statistics views