Re: Unexpected *ABORT STATE* - Mailing list pgsql-general

From Joseph Shraibman
Subject Re: Unexpected *ABORT STATE*
Date
Msg-id 3B65D118.AF419522@selectacast.net
Whole thread Raw
In response to Unexpected *ABORT STATE*  (Mike Finn <mike.finn@tacticalExecutive.com>)
Responses Re: Unexpected *ABORT STATE*  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-general
Mike Finn wrote:
>

> problem but I was wondering why this occurs, and if it is on the todo list to
> fix.

It occurs because once an error happens all the changes that have been
made may not mean anything, so the transaction must be rolled back.
Maybe there is something that could be set to interactive programs like
psql can disable this?  If not there should be, becuase I too have been
anoyed with a long interactive session having to be restarted because of
a typo.

--
Joseph Shraibman
jks@selectacast.net
Increase signal to noise ratio.  http://www.targabot.com

pgsql-general by date:

Previous
From: Joseph Shraibman
Date:
Subject: Re: HELP! BUG? pg_dump mucks up grant/revoke
Next
From: newsreader@mediaone.net
Date:
Subject: Re: database information