PG16: Prohibit use of multi-node #6190
Merged
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
force-pushed
the
pg16-remove-support-for-multinode
branch
2 times, most recently
from
ec5effa to
a437ddd
Compare
Codecov Report
@@ Coverage Diff @@
## main #6190 +/- ##
===========================================
- Coverage 81.47% 65.03% -16.44%
===========================================
Files 246 246
Lines 56985 56949 -36
Branches 12629 12620 -9
===========================================
- Hits 46426 37038 -9388
- Misses 8176 18038 +9862
+ Partials 2383 1873 -510
... and 91 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
from
a437ddd to
52a0e99
Compare
|
@mkindahl, @antekresic: please review this pull request.
|
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
from
52a0e99 to
d07c7b8
Compare
svenklemm
approved these changes
Oct 12, 2023
Sorry, what now? TimescaleDB is dropping multi node support? Is there any more info on that? 😮 |
mkindahl
reviewed
Oct 13, 2023
mkindahl
requested changes
Oct 13, 2023
erimatnor
reviewed
Oct 13, 2023
erimatnor
reviewed
Oct 13, 2023
erimatnor
changed the title
To speed up the release of support for PG16, we are not going to support multi-node when run on PG16. |
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
5 times, most recently
from
4b28cc0 to
b9b6434
Compare
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
3 times, most recently
from
27ba58a to
909aead
Compare
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
3 times, most recently
from
18a5eb3 to
28cc4de
Compare
fabriziomello
changed the title
mkindahl
approved these changes
Oct 16, 2023
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
8 times, most recently
from
275128c to
22dd9cc
Compare
Since multi-node is not supported on PG16, add errors to multi-node functions when run on this PostgreSQL version.
fabriziomello
force-pushed
the
pg16-remove-support-for-multinode
branch
from
22dd9cc to
9d680ef
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.
Since multi-node is not supported on PG16, add errors to multi-node functions when run on this PostgreSQL version.
Disable-check: force-changelog-file