Re: Assertion failure with a subtransaction and cursor

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Assertion failure with a subtransaction and cursor
Date: 2009-12-03 20:20:48
Message-ID: 4B181DA0.50707@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Ok, committed that way. I made the cross-check a WARNING. That seems
>> like the right level of seriousness, although I see that many of the
>> other similar checks are Asserts.
>
> Looks good. I'm a bit tempted to rename the interXact argument to
> something like noOwner --- no change in API, just name it a bit closer
> to what it actually does now. Thoughts?

Well, I did keep the cross-check at end-of-transaction, so it's not a
complete misnomer as it is; a file opened with interXact=false can't be
used across transactions. I won't object if you feel like renaming it,
though.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fredrik Palm 2009-12-03 20:58:24 Re: BUG #5229: Queing requests when not using psql
Previous Message David Gardner 2009-12-03 20:06:59 BUG #5232: plpythonu s=s.op() raises an exception