From: Peter Garner <peter.garner@toward.com>
To: pgsql-interfaces@postgresql.org
Cc: peter.garner@toward.com
Subject: aborted transactions
Date: Sun, 25 Oct 1998 12:34:14 EDT
Message-ID: <199810251234.AA50923204@piglet.toward.com> (raw)
Hi All! :-)
I am using the libpq C interface to access postgres from C++.
I am VERY impressed with postgres!!!
Although postgres does not seem to support nested
transactions, it does support serialized, non nested
transactions. However, it seems to me that if certain
queries fail, the current transaction is aborted and all
queries are ignored until the transaction is ended, either
via commit or rollback. At least that is what seems to be
happening. The following message is printed after every
query (after a failing query) until the transaction is over,
and it does seem that queries are ignored until the end of
transaction :
NOTICE: (transaction aborted): queries ignored until END
So is there anyway to alter this behaviour or should I code
like this will always happen. Also if there is no begin
transaction block, I assume that each statement is a unit
of work and that all subsequent queries will work. I.e. it
would be absurd if one failed query caused all subsequent
queries to be ignored until the connection closed. Is this
correct?
Thank you
Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: peter.garner@toward.com
Subject: Re: aborted transactions
In-Reply-To: <199810251234.AA50923204@piglet.toward.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox