Move partialize functions to _timescaledb_functions schema #6020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@fabriziomello, @konskov: please review this pull request.
|
mkindahl
approved these changes
Aug 29, 2023
fabriziomello
approved these changes
Aug 29, 2023
jnidzwetzki
approved these changes
Aug 29, 2023
svenklemm
force-pushed
the
schema_partialize
branch
3 times, most recently
from
971ecaa
to
8f56468
Compare
Codecov Report
@@ Coverage Diff @@
## main #6020 +/- ##
==========================================
- Coverage 87.11% 79.48% -7.64%
==========================================
Files 243 243
Lines 55993 48799 -7194
Branches 12398 12195 -203
==========================================
- Hits 48780 38786 -9994
+ Misses 4871 4188 -683
- Partials 2342 5825 +3483
... and 220 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
svenklemm
force-pushed
the
schema_partialize
branch
from
8f56468
to
6cf0cf1
Compare
svenklemm
force-pushed
the
schema_partialize
branch
from
6cf0cf1
to
0f42af3
Compare
To increase schema security we do not want to mix our own internal objects with user objects. Since chunks are created in the _timescaledb_internal schema our internal functions should live in a different dedicated schema. This patch make the necessary adjustments for the following functions: - finalize_agg_ffunc(internal,text,name,name,name[],bytea,anyelement) - finalize_agg_sfunc(internal,text,name,name,name[],bytea,anyelement) - partialize_agg(anyelement) - finalize_agg(text,name,name,name[][],bytea,anyelement)
svenklemm
force-pushed
the
schema_partialize
branch
from
0f42af3
to
70f1024
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To increase schema security we do not want to mix our own internal objects with user objects. Since chunks are created in the _timescaledb_internal schema our internal functions should live in a different dedicated schema. This patch make the necessary adjustments for the following functions:
Disable-check: force-changelog-file