pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chip Gobs <chip.gobs@noaa.gov>
To: pgsql-sql@postgresql.org
Subject: Implicit Transactions
Date: Fri, 17 Sep 2004 10:44:14 -0400
Message-ID: <414AF83E.AFA00204@noaa.gov> (raw)


We are porting from Informix to  PostgreSQL 7.4.5 and have noticed the
following behavior.

If we try to OPEN a CURSOR  for an invalid SELECT statement in ECPG, we
get an error, as expected.  However, if we then
attempt to OPEN another CURSOR  for a valid statement, we get an error
that says we are in a failed transaction.   At that point, no statement
will succeed.   The only way we have found to get out of this state is
to ROLLBACK explicitly.

We are not using explicit transactions.  My understanding is that PG
should be rolling back failed statements when we are not in an
explicit transaction.

Do we have an incorrect setting, a misunderstanding of how it is
supposed to work, or a bug? Could anyone enlighten me?

Thanks,

Chip




view thread (2+ messages)  latest in thread

Message-ID: <414AF83E.AFA00204@noaa.gov>
Permalink:  ../414AF83E.AFA00204@noaa.gov/
Also on:    postgresql.org/message-id/414AF83E.AFA00204@noaa.gov

 · 

reply

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-sql@postgresql.org
  Cc: chip.gobs@noaa.gov
  Subject: Re: Implicit Transactions
  In-Reply-To: <414AF83E.AFA00204@noaa.gov>

* 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