From: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: auto_explain log_verbose causes regression failure |
Date: | 2010-02-24 01:54:01 |
Message-ID: | 20100224105400.9734.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)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(dot)500A37541C5(at)cvs(dot)postgresql(dot)org>
- Fix ExecEvalArrayRef to pass down the old value of the array element or slice being assigned to
Message-Id: <20100218184147(dot)A9EC97541C5(at)cvs(dot)postgresql(dot)org>
> ---------------------------------------------------------------------------
>
> Itagaki Takahiro wrote:
> >
> > Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-02-24 02:15:59 | pgsql: Un-break pg_dump for the case of zero-column tables. |
Previous Message | Josh Berkus | 2010-02-24 01:46:26 | Re: pg_stop_backup does not complete |