Message-Id: <4BFD02770200002500031AFF@gw.wicourts.gov>
Date: Wed, 26 May 2010 11:13:59 -0500
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Ravi Katkar" <Ravi.Katkar@infor.com>,
	"'pgsql-admin@postgresql.org'" <pgsql-admin@postgresql.org>
Subject: Re: Transaction with in function
References: <46AC8D44F3AE1F4888F137837D0DF635072561999F@INHYWEXMB2.infor.com>
In-Reply-To: <46AC8D44F3AE1F4888F137837D0DF635072561999F@INHYWEXMB2.infor.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Ravi Katkar <Ravi.Katkar@infor.com> wrote:
 
> I know that postgresql does not support nested transactions,
> 
> I looking for solution for commit, rollback with in function. May
> be using the save point.
 
That is essentially the same as nested transactions, isn't it?  Just
using SQL standard syntax?
 
> I were to use save point in function , when it would get commit.?
 
Each savepoint creates a subtransaction which will be included in
the top level transaction unless it or an intermediate savepoint is
rolled back.  Nothing from the top level transaction is visible to
other transactions until the commit of the top level transaction.
 
If this and the docs don't make it clear, please post again:
 
http://www.postgresql.org/docs/8.4/interactive/sql-savepoint.html
 
If you do post again, please include your PostgreSQL version and an
explanation of what problem you're trying to solve.  More specific
questions tend to elicit more useful responses:
 
-Kevin