Changes between Initial Version and Version 1 of Ticket #4608, comment 1


Ignore:
Timestamp:
12/25/19 15:09:13 (5 years ago)
Author:
robe

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4608, comment 1

    initial v1  
    55PostgreSQL 12.1, compiled by Visual C++ build 1914, 64-bit POSTGIS="3.0.0 r17983" [EXTENSION] PGSQL="120" GEOS="3.8.0-CAPI-1.13.1 " PROJ="Rel. 5.2.0, September 15th, 2018" GDAL="GDAL 2.4.3, released 2019/10/28" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.4.3 (Internal)" TOPOLOGY RASTER
    66}}}
     7
     8{{{
     9ERROR:  no spatial operator found for opfamily 51535 strategy 7
     10SQL state: XX000
     11}}}
     12
     13and on my
     14
     15
     16{{{
     17PostgreSQL 12.1 (Ubuntu 12.1-1.pgdg18.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0, 64-bit POSTGIS="3.0.0 r17983" [EXTENSION] PGSQL="120" GEOS="3.7.1-CAPI-1.11.1 27a5e771" PROJ="Rel. 4.9.3, 15 August 2016" LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.2.1" WAGYU="0.4.3 (Internal)" (core procs from "3.0.0rc1 r17886" need upgrade)
     18}}}
     19
     20I get:
     21{{{
     22ERROR:  no spatial operator found for opfamily 19319 strategy 7
     23}}}
     24
     25so it seems the opfamily is probably tied to the table oid?