Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grant USAGE on debug schema #7265

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

erimatnor
Copy link
Contributor

@erimatnor erimatnor commented Sep 11, 2024

Make it possible for regular users to execute functions in the schema _timescaledb_debug.

As a consequence, the extension_state() function in this schema can now be executed by "public". This is the only function in this schema and there is no security risk in making it accessible.

Disable-check: force-changelog-file

@erimatnor erimatnor added the debugging Issues related to introduction of or needing debugging support label Sep 11, 2024
@erimatnor erimatnor self-assigned this Sep 11, 2024
Copy link

codecov bot commented Sep 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.33%. Comparing base (59f50f2) to head (fc5d07d).
Report is 348 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #7265       +/-   ##
===========================================
+ Coverage   80.06%   92.33%   +12.26%     
===========================================
  Files         190      205       +15     
  Lines       37181    38433     +1252     
  Branches     9450     9962      +512     
===========================================
+ Hits        29770    35487     +5717     
+ Misses       2997     2946       -51     
+ Partials     4414        0     -4414     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@svenklemm
Copy link
Member

Hmm why do we need another schema with the same setup like _timescaledb_functions. If public gets access to those why not add it to _timescaledb_functions?

@erimatnor
Copy link
Contributor Author

Hmm why do we need another schema with the same setup like _timescaledb_functions. If public gets access to those why not add it to _timescaledb_functions?

The schema is there, and we intend to add more debug functions to it.

We can always reconsider the use of this schema later. So feel free to file an issue for that @svenklemm .

Make it possible for regular users to execute functions in the schema
`_timescaledb_debug`.

As a consequence, the `extension_state()` function in this schema can
now be executed by "public". This is the only function in this schema
and there is no security risk in making it accessible.
@erimatnor erimatnor merged commit 616080e into timescale:main Sep 19, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debugging Issues related to introduction of or needing debugging support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants