[PostGIS] #6038: Using public.geometry_columns causes 'could not open relation with OID 188954716' after drop geometry tables
PostGIS
trac at osgeo.org
Fri Jan 23 04:00:13 PST 2026
#6038: Using public.geometry_columns causes 'could not open relation with OID
188954716' after drop geometry tables
--------------------------------+---------------------
Reporter: Lars Aksel Opsahl | Owner: pramsey
Type: defect | Status: new
Priority: blocker | Milestone:
Component: postgis | Version: master
Resolution: | Keywords:
--------------------------------+---------------------
Comment (by Lars Aksel Opsahl):
I picked out the values of oid's before running
ERROR: XX000: could not open relation with OID 188967326 and that OID was
connected to "gsk_utdata_25_784.edge_attributes" table .
{{{
\d gsk_utdata_25_784.edge_attributes
Unlogged table
"gsk_utdata_25_784.edge_attributes"
Column | Type | Collation | Nullable |
Default
---------+-----------------------+-----------+----------+---------------------------------------------------------------
id | integer | | not null |
nextval('gsk_utdata_25_784.edge_attributes_id_seq'::regclass)
id_test | integer | | |
geo | topology.topogeometry | | |
Indexes:
"edge_attributes_pkey" PRIMARY KEY, btree (id)
Check constraints:
"check_topogeom_geo" CHECK ((geo).topology_id = 3 AND (geo).layer_id =
1 AND (geo).type = 2)
}}}
To reproduce the error it was enought to drop this table.
{{{
DROP TABLE gsk_utdata_25_784.edge_attributes CASCADE ;
}}}
And the command in session did hang
{{{
select SRID from public.geometry_columns where (f_table_schema = 't1') and
f_table_name = 'edge_data' and f_geometry_column = 'geom';
}}}
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/6038#comment:7>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list