SloNN
commented
3 weeks ago I noticed that queries to regular YDB tables work fine, queries to table pg_namespace work fine.
All problems with access occur only to the pg_class table.
/olap-testing-vla-common2/kikimr/apkobzev/test=> select * from test_row;
a
---
1
(1 row)
/olap-testing-vla-common2/kikimr/apkobzev/test=> SELECT * FROM pg_namespace ;
nspacl | nspname | nspowner | oid
--------+--------------------+----------+------
| information_schema | 1 | 1
| public | 1 | 2200
| pg_catalog | 1 | 11
(3 rows)
/olap-testing-vla-common2/kikimr/apkobzev/test=> SELECT * FROM pg_class ;
Status: ABORTED
Issues:
<main>: Error: Check failed: path: '/olap-testing-vla-common2', error: path hasn't been resolved, nearest resolved path: '' (id: <Invalid>)
<main>: Error: Query invalidated on scheme/internal error during Data execution, code: 2019
/olap-testing-vla-common2/kikimr/apkobzev/test=>
While receiving table List from YDB Database over PG protocol, SuperSet makes the query below. This query commonly fails, but sometimes this query works. It seems that it depends on session parameters