| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com> |
| Cc: | "stepya(at)ukr(dot)net" <stepya(at)ukr(dot)net>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker |
| Date: | 2017-03-07 18:16:03 |
| Message-ID: | 29113.1488910563@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com> writes:
> It quite difficult to reproduce.
> The only observation. Usually it crashes with parallelism only on quite big tables with inheritance .
If you can't extract a test case, one thing that would be quite helpful is
to get a stack trace from the point of the error. There are only four
occurrences of
elog(ERROR, "invalid cache ID: %d", cacheId);
and they're all in src/backend/utils/cache/syscache.c. If you could
change those to elog(PANIC, ...) in a debug-enabled build, run till
you get the failure, and then use gdb to get a backtrace from the
ensuing core dump, that might be enough info to fix it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mdudley | 2017-03-08 16:56:59 | BUG #14582: ecpg crashes on SQL input |
| Previous Message | Stepan Yankevych | 2017-03-07 18:01:49 | Re: BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker |