Re: Re: Re: Re: Re: Bug: ERROR: invalid cache ID: 42 CONTEXT:parallel worker
От | Thomas Munro |
---|---|
Тема | Re: Re: Re: Re: Re: Bug: ERROR: invalid cache ID: 42 CONTEXT:parallel worker |
Дата | |
Msg-id | CAEepm=3TJtzvvk-g84a8VPLSv79oxkeP5YU7tGF1waE8Na83gA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re:Re: Re: Re: Re: Bug: ERROR: invalid cache ID: 42 CONTEXT:parallel worker (jimmy <mpokky@126.com>) |
Ответы |
Re: Re: Re: Re: Re: Bug: ERROR: invalid cache ID: 42 CONTEXT:parallel worker
|
Список | pgsql-bugs |
On Mon, Aug 27, 2018 at 6:07 PM jimmy <mpokky@126.com> wrote: > Let explain it.When I use postgresql-10.4-1-linux-x64.run to install. > There does not use source code to compile, and make , make install. It is like a windows program. I just click next stepbutton. > The database was installed from the ui interface step by step. Hi Jimmy, Just want to double check something: are you sure you're using oracle_fdw 2.0.0? It seems that the earlier versions suffered from a problem with exactly the symptom you describe (except the error said 41 instead of 42, but that's expected because the enumerator values moved): https://www.postgresql.org/message-id/11960.1511116873%40sss.pgh.pa.us But that was fixed here: https://github.com/laurenz/oracle_fdw/commit/4accfebb33c316d71da73d341dac796df813638c The problem was that it tried to access the system caches from _PG_init(). It wouldn't matter if you were querying an oracle_fdw table or not, it'd only matter if that library had been loaded in the leader process, because that would cause the parallel workers to load it, run _PG_init(), and blow up. -- Thomas Munro http://www.enterprisedb.com
В списке pgsql-bugs по дате отправления: