chore: use _supabase database for internals #2707
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
This is to avoid overloading our user postgres database with every new addition to _analytics or _realtime
Pull Request Test Coverage Report for Build 11074018500Details
💛 - Coveralls |
avallete
commented
Sep 24, 2024
internal/start/start.go
Outdated
| @@ -750,7 +750,7 @@ EOF | |||
| fmt.Sprintf("DB_PORT=%d", dbConfig.Port), | |||
| "DB_USER=supabase_admin", | |||
| "DB_PASSWORD=" + dbConfig.Password, | |||
| "DB_NAME=" + dbConfig.Database, | |||
There was a problem hiding this comment.
realtime schema should be initialised inside the postgres database. We probably need to check with @filipecabaco if there's additional config for separating the control plane database.
psql (16.3, server 15.6)
Type "help" for help.
_supabase=> \dn
List of schemas
Name | Owner
------------+-------------------
_analytics | postgres
_realtime | postgres
_supavisor | postgres
public | pg_database_owner
realtime | postgres
(5 rows)
_supabase=> \dt realtime.*
List of relations
Schema | Name | Type | Owner
----------+-------------------+-------+-------------------------
realtime | messages | table | supabase_realtime_admin
realtime | schema_migrations | table | supabase_admin
realtime | subscription | table | supabase_admin
(3 rows)
sweatybridge
approved these changes
Sep 27, 2024
Co-authored-by: Han Qiao <[email protected]>
avallete
deleted the
avallete/chore-create-new-supabase-management-database
branch
avallete
added a commit
to supabase/supabase
that referenced
this pull request
Sep 30, 2024
Following: supabase/cli#2707 BREAKING CHANGES: When migrating from an older version you will need to manually create the new internal _supabase database and analytics schema the same way the and do. Via:
3 tasks
avallete
added a commit
to supabase/supabase
that referenced
this pull request
Oct 8, 2024
* chore: move _analytics to a distinct database Following: supabase/cli#2707 BREAKING CHANGES: When migrating from an older version you will need to manually create the new internal _supabase database and analytics schema the same way the and do. Via: * feat: add supavisor to the self-hosted stack * chore(docs): add docs about supavisor * chore: fix reviewdog warning * chore: fix typo * chore: apply pr comments
encima
pushed a commit
to supabase/supabase
that referenced
this pull request
Nov 19, 2024
* chore: move _analytics to a distinct database Following: supabase/cli#2707 BREAKING CHANGES: When migrating from an older version you will need to manually create the new internal _supabase database and analytics schema the same way the and do. Via: * feat: add supavisor to the self-hosted stack * chore(docs): add docs about supavisor * chore: fix reviewdog warning * chore: fix typo * chore: apply pr comments
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.
This is to avoid overloading our user postgres database with every new addition to _analytics or _realtime
What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.