Re: BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker

Unfortunately it is almost impossible.
We experiencing such error on our PROD env only (starting from 9.6.0 version )

I will think about debug-enabled build on some of our dev environment, but not sure if we can reproduce it there due to much less amount of data.

Best Regards,
Stepan Yankevych
Lead Software Engineer

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, March 7, 2017 20:16 PM
To: Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com>
Cc: stepya(at)ukr(dot)net; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker

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