Bruce Momjian <br...@momjian.us> wrote:
> Uh, I don't see this patch as applied. Was it not necessary?
No, the bug was reported again and fixed then with:
- Force READY portals into FAILED state when a transaction or subtransaction
is aborted
Message-Id: <20100218030646.500a3754...@cvs.postgresql.org>
- Fix ExecEvalArrayRef to pass down the old value of the array element or
slice being assigned to
Message-Id: <20100218184147.a9ec9754...@cvs.postgresql.org>
> ---------------------------------------------------------------------------
>
> Itagaki Takahiro wrote:
> >
> > Robert Haas <robertmh...@gmail.com> wrote:
> >
> > > It looks like this is enough to reproduce the cache lookup failure:
> >
> > The "cache loopup failure" part could be fixed by the attached patch.
> > It forbids explaining if the transaction is in error state.
> >
> > I cannot reproduce "unexpected refassgnexpr" and "unexpected FieldStore"
> > errors yet. We might need another fix for them.
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
