Re: Making a result of transaction visible to everyone, saving the ability for a rollback - Mailing list pgsql-general

From Sam Mason
Subject Re: Making a result of transaction visible to everyone, saving the ability for a rollback
Date
Msg-id 20090212121128.GM3008@frubble.xen.chris-lamb.co.uk
Whole thread Raw
In response to Making a result of transaction visible to everyone, saving the ability for a rollback  (Igor Katson <descentspb@gmail.com>)
List pgsql-general
On Wed, Feb 11, 2009 at 12:58:53PM +0300, Igor Katson wrote:
> I want to make the result of a transaction, in which this function is
> executed, visible to the outer clients, but to have the ability of
> making a rollback in case one of the clients says something went wrong.
> Is it possible to do that?

You can't use ROLLBACK to accomplish that; transactional semantics are
an all or nothing affair.  For example, if another transaction writes
results from this intermediate transaction back into the database how
does the database know what you really want to get rid of when you
rollback.

A possible solution would be to perform a backup or use point in
time recovery to be able to get the whole database back to the state
beforehand.


  Sam

pgsql-general by date:

Previous
From: Sim Zacks
Date:
Subject: row constructors
Next
From: Gurjeet Singh
Date:
Subject: Fwd: Need help in porting Oracle PL/SQL's OUT paramater based procedures