Re: Unexpected *ABORT STATE*

From: Joseph Shraibman <jks(at)selectacast(dot)net>
To: Mike Finn <mike(dot)finn(at)tacticalExecutive(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unexpected *ABORT STATE*
Date: 2001-07-30 21:26:48
Message-ID: 3B65D118.AF419522@selectacast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message newsreader 2001-07-30 21:34:53 Re: database information
Previous Message Joseph Shraibman 2001-07-30 21:22:47 Re: HELP! BUG? pg_dump mucks up grant/revoke