From: | Mike Finn <mike(dot)finn(at)tacticalExecutive(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Unexpected *ABORT STATE* |
Date: | 2001-07-30 16:27:24 |
Message-ID: | 01073010272406.04601@birch.tacticalExecutive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Seems that during an interactive transaction at the psql prompt
any syntax error will cause the following state to be entered
NOTICE: current transaction is aborted, queries ignored until end of
transaction block
*ABORT STATE*
This is a bit annoying since it reared up near the end of a long and complex
data manipulation session. I don't want to be at all pushy (just about
anything else is probably higher priority) and stress that Its not a big
problem but I was wondering why this occurs, and if it is on the todo list to
fix.
here is a sample
gbtest=> begin;
BEGIN
gbtest=> select * fro pg_trigger;
ERROR: parser: parse error at or near "fro"
gbtest=> select * from pg_trigger;
NOTICE: current transaction is aborted, queries ignored until end of
transaction block
*ABORT STATE*
gbtest=> rollback;
Mike.
===================
Mike Finn
Tactical Executive Systems
mike(dot)finn(at)tacticalExecutive(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-07-30 16:50:28 | Re: Re: "Oracle's ROWNUM" |
Previous Message | Tom Lane | 2001-07-30 14:50:50 | Re: Re: "Oracle's ROWNUM" |