You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change removes a check for `USAGE` privileges on data nodes
required to query the data node using utility commands, such as
`hypertable_size`. Normally, PostgreSQL doesn't require `USAGE` on a
foreign server to query its remote tables. Also, size utilities, like
`pg_table_size` can be used by anyone---even roles without any
privileges on a table. The behavior on distributed hypertables is now
consistent with PostgreSQL.
Fixestimescale#3698
erimatnor
added a commit
to erimatnor/timescaledb
that referenced
this issue
Oct 15, 2021
This change removes a check for `USAGE` privileges on data nodes
required to query the data node using utility commands, such as
`hypertable_size`. Normally, PostgreSQL doesn't require `USAGE` on a
foreign server to query its remote tables. Also, size utilities, like
`pg_table_size` can be used by anyone---even roles without any
privileges on a table. The behavior on distributed hypertables is now
consistent with PostgreSQL.
Fixestimescale#3698
This change removes a check for `USAGE` privileges on data nodes
required to query the data node using utility commands, such as
`hypertable_size`. Normally, PostgreSQL doesn't require `USAGE` on a
foreign server to query its remote tables. Also, size utilities, like
`pg_table_size` can be used by anyone---even roles without any
privileges on a table. The behavior on distributed hypertables is now
consistent with PostgreSQL.
Fixes#3698
Relevant system information:
TimescaleDB 2.4
Describe the bug
Calling
hypertable_size
on a distributed hypertable with no priviliges on the foreign servers returns weird result:Without privileges:
With privileges:
To Reproduce
See above.
Expected behavior
The
hypertable_size
function should raise an error if privileges are missing.Actual behavior
The function returns the wrong result.
The text was updated successfully, but these errors were encountered: