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
I noticed that for the TimescaleDB Docker image, the TIMESCALEDB_ENABLED environment variable is explicitly set to append 'timescaledb' to "shared_preload_libraries" in the Postgres config.
I'd like to install other Postgres extensions in my own custom Docker image such as pg_stat_monitor or pg_safeupdate which requires overwriting Postgres' config with shared_preload_libraries.
fly pg config exists, though I would prefer not to have to manually re-configure my Postgres cluster every time I re-deploy a new one.
Are there any ways to make Postgres configuration changes right from the Docker image and ensure that it persists throughout a deployed Fly.io Postgres cluster?
The text was updated successfully, but these errors were encountered:
I noticed that for the TimescaleDB Docker image, the TIMESCALEDB_ENABLED environment variable is explicitly set to append 'timescaledb' to "shared_preload_libraries" in the Postgres config.
I'd like to install other Postgres extensions in my own custom Docker image such as pg_stat_monitor or pg_safeupdate which requires overwriting Postgres' config with shared_preload_libraries.
fly pg config
exists, though I would prefer not to have to manually re-configure my Postgres cluster every time I re-deploy a new one.Are there any ways to make Postgres configuration changes right from the Docker image and ensure that it persists throughout a deployed Fly.io Postgres cluster?
The text was updated successfully, but these errors were encountered: