You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The documentation for Services has an example of running timescaledb that uses initialScript to create the extension. However, initialScript is only run against the default database named postgres, meaning that the timescaledb extensions are not available to the other databases ("mydb" in the Services documentation example).
It can be seen that the timescaledb extension is not actually loaded for the mydb database (initialDatabases[0]), but it is available under the databased named postgres.
$ psql --dbname mydb --command="SELECT installed_version FROM pg_available_extensions WHERE name = 'timescaledb';"
installed_version
-------------------
(1 row)
$ psql --dbname postgres --command="SELECT installed_version FROM pg_available_extensions WHERE name = 'timescaledb';"
installed_version
-------------------
2.17.2
(1 row)
Version
devenv 1.3.1 (x86_64-linux)
I think this is a matter of the documentation being lacking. There is nothing in the documentation to suggest which database initialScript is being applied against. After digging into the source I think my expected behaviour was wrong, but I wanted to flag up my troubles here as I think I'm not the only one who has run into the same misunderstanding.
The text was updated successfully, but these errors were encountered:
Describe the bug
The documentation for Services has an example of running timescaledb that uses
initialScript
to create the extension. However,initialScript
is only run against the default database namedpostgres
, meaning that the timescaledb extensions are not available to the other databases ("mydb" in the Services documentation example).To reproduce
https://gist.github.com/CalebJohn/6bd1cfc8c4daff6a849ddf7e17d1ecf8
Run
devenv up
.It can be seen that the timescaledb extension is not actually loaded for the mydb database (
initialDatabases[0]
), but it is available under the databased named postgres.Version
devenv 1.3.1 (x86_64-linux)
I think this is a matter of the documentation being lacking. There is nothing in the documentation to suggest which database
initialScript
is being applied against. After digging into the source I think my expected behaviour was wrong, but I wanted to flag up my troubles here as I think I'm not the only one who has run into the same misunderstanding.The text was updated successfully, but these errors were encountered: