Re: Autocommit off - commits/rollbacks

From: tushar nehete <tpnehete(at)gmail(dot)com>
To: Jerry Sievers <gsievers19(at)comcast(dot)net>
Cc: "Vogt, Michael" <Michael(dot)Vogt(at)united-security-providers(dot)ch>, pgsql-general(at)postgresql(dot)org
Subject: Re: Autocommit off - commits/rollbacks
Date: 2011-03-29 11:35:04
Message-ID: AANLkTikqL4dpK5q4hAXn7EhuAjAGHMkdsG4i-pC4hA_g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yes We can use exception for each statement to restrict the rollback.
But how we can use SAVEPOINT and rollback to SAVEPOINT
in the stored function or procedure in POSTGRES?
We can only use the savepoints in transactions but not in stored functions.

Regards,
Tushar

On Tue, Mar 29, 2011 at 12:54 PM, Jerry Sievers <gsievers19(at)comcast(dot)net>wrote:

> Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
>
> > On 03/14/2011 10:55 PM, Vogt, Michael wrote:
> >
> >> Hey all
> >>
> >> I have a question, using the autocommit off option in postgres.
> >>
> >> As starting position I use a table called xxx.configuration using a
> >> unique id constraint.
> >>
> >> Why does postgres rollback the whole transaction after an error?
> >
> > It's a PostgreSQL limitation (or, arguably, optimization). When a
>
> Well, any transactional RDBMS whatsoever should behave that way. Hardly
> a PostgreSQL exclusive feature :-)
>
> --
> Jerry Sievers
> e: gsievers19(at)comcast(dot)net
> p: 305.321.1144
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Maximilian Tyrtania 2011-03-29 13:07:04 anonymous record as an in parameter
Previous Message Zheng Yang 2011-03-29 11:28:57 Re: foreign data wrappers