Re: Now PostgreSQL recovers from errors within trns

From: hstenger(at)adinet(dot)com(dot)uy
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Now PostgreSQL recovers from errors within trns
Date: 2000-07-31 17:10:16
Message-ID: 3985B2F8.BE27998A@adinet.com.uy
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> hstenger(at)adinet(dot)com(dot)uy writes:
> > My goal is to make the backend accept erroneous commands, not falling
> > in *ABORT STATE*, but rolling back automatically, & continue accepting
> > commands.
>
> The way you're doing it, you might as well just not use transaction
> blocks at all. I don't think wiping out the effects of all preceding
> commands within the transaction counts as "recovering from an error".

Ok, maybe I exagerated, but kind of solves my problem. GeneXus, my CASE tool,
will send begin/commit pairs, so I must 'recover' automatically. I aimed
DB2-like behaviour, which I was told, aborts on errors within transactions, but
remains in a runnable state. Don't you consider it valueable whatsoever?

Haroldo.

--
----------------------+------------------------
Haroldo Stenger | hstenger(at)ieee(dot)org
Montevideo, Uruguay. | hstenger(at)adinet(dot)com(dot)uy
----------------------+------------------------
Visit UYLUG Web Site: http://www.linux.org.uy
-----------------------------------------------

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message hstenger 2000-07-31 17:30:40 Re: Now PostgreSQL recovers from errors within trns
Previous Message Don Baccus 2000-07-31 17:05:12 Re: Now PostgreSQL recovers from errors within trns