Re: Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0”

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Joao Ferreira <jpgferreira(at)yahoo(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0”
Date: 2019-06-20 09:16:44
Message-ID: CAPmGK15z66yN9e=PU4pSpSi6Qs5NG+J4MoEOCLDB79ESadPG0A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jun 18, 2019 at 9:22 PM Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Tue, Jun 18, 2019 at 8:02 AM Joao Ferreira <jpgferreira(at)yahoo(dot)com> wrote:
>> I'm using PostgreSQL 11.3 and I want to access a table in another Postgres database using postgres_fdw but since the original table has an SP-GiST index on a geometry column, the query on the foreign table fails with "ERROR: cache lookup failed for type 0", even if the table is empty (Step 7). This doesn't happen if the query is done directly to the remote table (Steps 3 and 6) or if the remote table doesn't have the index (Steps 3 and 4).

I started working on this.

> I've verified this on ubuntu 18.04 with 11.3 installed from PGDG apt repo, and attached a single-file reproduction.

I've also verified this on my environment with PG 11.4.

> If I change from sp-gist to just gist, there is no problem. And if I change to indexing a built-in sp-gist operator class (point rather than geom), there is also no problem.

Verified.

Will continue investigations.

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2019-06-20 09:57:22 Logging corruption error codes
Previous Message Jorge Gustavo Rocha 2019-06-20 08:48:25 Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2