What
If you look at values.yaml, you'll see where we CREATE EXTENSION ... that we install them in the paradedb database. In Postgres, when a database gets created it does so from a database called template1. What this means is that if we install our extensions in template1, any new database created will automatically have the extension created, which is a better UX.
We should investigate whether:
[ ] Is this required here? Try creating a new database from inside the cluster and see if the extensions are already loaded.
[ ] If they are not, see if we can install them on the template1 database. Perhaps we can do something similar to what we do for setting the search_path.
philippemnoel
commented
1 week ago
What If you look at
values.yaml, you'll see where weCREATE EXTENSION ...that we install them in theparadedbdatabase. In Postgres, when a database gets created it does so from a database calledtemplate1. What this means is that if we install our extensions intemplate1, any new database created will automatically have the extension created, which is a better UX.We should investigate whether:
template1database. Perhaps we can do something similar to what we do for setting thesearch_path.Why ^
How Unclear