Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

pgr_getTableName fails when current user is not owner of a table's schema

未关闭
#241 12 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
postgresql
领域
backend, databases

调研方向

The function pgr_getTableName is likely in the SQL source files (look for .sql files defining functions). Examine its query on information_schema.schemata and compare with pg_catalog.pg_namespace for broader schema visibility. Test by creating a non-owner role with SELECT privileges and verifying the fix returns schema and table names correctly.

由索引模型根据 Issue 内容生成。

描述

Deprecation Function/Internal Functionality Request

When the current role accessing the database is not the owner of the schema where a table lives, pgr_getTableName returns null, null, even though the table exists, and is readable to the role.

I believe this is because pgr_getTableName reads from information_schema.schemata, which only lists schemas actually owned by the current role, not all schemas accessible.

example: user1 is the owner of a database, and thus is owner of the public schema. user2 has read access to the public schema.

as user1:

db_name=# select * from pgr_getTableName('edge_table');
sname  |   tname    
--------+------------
public | edge_table
(1 row)

as user2:

db_name=> select * from pgr_getTableName('edge_table');
sname | tname 
-------+-------
         | 
(1 row)
主要语言
C++
星标
1.4k
派生
397
平均合并
2 天 2 小时
30 天内合并 PR
4

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pgRouting/pgrouting 的其他 Issue

查看 pgRouting/pgrouting 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。