From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | stepya(at)ukr(dot)net, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker |
Date: | 2017-11-20 09:39:13 |
Message-ID: | 1511170753.2615.4.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
stepya(at)ukr(dot)net wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14581
> Logged by: Stepan Yankevych
> Email address: stepya(at)ukr(dot)net
> PostgreSQL version: 9.6.2
> Operating system: RedHat
> Description:
>
> Time to time i have invalid cache ID: 41 while running simple query with
> parallelism.
> for example
> select count(1) from client_order where date_id = 20170301;
> Crashes with (see error log)
>
> < 2017-03-07 08:57:45.312 EST >ERROR: invalid cache ID: 41
> < 2017-03-07 08:57:45.312 EST >ERROR: invalid cache ID: 41
> < 2017-03-07 08:57:45.312 EST >ERROR: invalid cache ID: 41
> < 2017-03-07 08:57:45.312 EST >ERROR: invalid cache ID: 41
> < 2017-03-07 08:57:45.312 EST >ERROR: invalid cache ID: 41
> < 2017-03-07 08:57:45.312 EST [unknown] SELECT>ERROR: invalid cache ID: 41
>
> < 2017-03-07 08:57:45.312 EST [unknown] SELECT>CONTEXT: parallel worker
> < 2017-03-07 08:57:45.312 EST [unknown] SELECT>STATEMENT: select count(1)
Could it be that the oracle_fdw extension was loaded?
There was a bug reported yesterday that would explain this error:
https://github.com/laurenz/oracle_fdw/issues/215
If oracle_fdw is involved, the latest commit should fix the problem.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-11-20 13:09:28 | Re: BUG #14919: Invalid column in sub select is still a valid select |
Previous Message | Boris Sagadin | 2017-11-20 08:24:53 | Re: BUG #14917: process hang on create index |