From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Intermittent "cache lookup failed for type" buildfarm failures |
Date: | 2016-08-16 19:03:16 |
Message-ID: | 20160816190316.GA838146@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > It would sure be nice if those cache lookup failure messages printed
> > the file and line number. I wonder if we could teach psql to always
> > treat the VERBOSITY as verbose when the error code is XX000.
>
> I looked around when I saw the earlier ones of these, and had more or less
> convinced myself that the errors were probably coming from one of the
> lsyscache.c convenience subroutines. If that's true, we'd need a stack
> trace to have much hope of identifying the cause.
Maybe we can have a code path that calls backtrace() somewhere in
errfinish, for platforms that support that. At least grouse uses gcc,
so I suppose it must also use glibc.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Shay Rojansky | 2016-08-16 19:16:08 | Re: Slowness of extended protocol |
Previous Message | Robert Haas | 2016-08-16 18:54:52 | Re: Declarative partitioning - another take |