Re: [BUGS] BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker
От | Stepan Yankevych |
---|---|
Тема | Re: [BUGS] BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker |
Дата | |
Msg-id | AM3PR03MB09658F63939910557B049AC892210@AM3PR03MB0965.eurprd03.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
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 muchless amount of data. Best Regards, Stepan Yankevych Lead Software Engineer -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, March 7, 2017 20:16 PM To: Stepan Yankevych <Stepan_Yankevych@epam.com> Cc: stepya@ukr.net; pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker Stepan Yankevych <Stepan_Yankevych@epam.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-enabledbuild, run till you get the failure, and then use gdb to get a backtrace from the ensuing core dump, that mightbe enough info to fix it. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: