![]() Postgres 9.3 introduced data checksums for early data corruption detection. If you use Heroku Connect to sync Salesforce data with your database, see Heroku Connect’s article on upgrading the Heroku Postgres database version. Requires downtime of about 3 minutes per GB, although this amount can vary substantially. Not supported for Shield-tier plans because PGBackups don’t work with Shield databases. Works for Essential, Standard, Premium, and Private-tier Heroku Postgres plans, but only for databases under 10 GB. Requires downtime of about 30 minutes, although this amount can vary. Checksums are disabled in your database.Works for all Heroku Postgres plans except Essential-tier plans. Both methods require some application downtime to ensure that no data is lost during the upgrade. Heroku supports two methods for upgrading. It’s a significant operation that must be done with care. Upgrading your major PostgreSQL version can be done only via the Heroku CLI. To use SSL certificate validation, you’ll need to use the MB_DB_CONNECTION_URI method to configure your database connection.If you want to upgrade your database’s minor version, or if you only want to change your Postgres plan or underlying infrastructure, see Changing the Plan or Infrastructure of a Heroku Postgres Database. How you configure your connection depends on whether you’re using Postgres as Metabase’s application database or as a data warehouse connected to Metabase: We’re including it here only to assist in troubleshooting, or for situations in which security is not a priority. Or manually enabling the NonValidatingFactory.Configuring the PostgreSQL connection to use SSL certificate validation,.You can resolve this failure in one of two ways: It’s possible that you could experience a failure either at startup (if you’re using a PostgreSQL application database) or when querying a PostgreSQL data warehouse. If you’re upgrading from a previous version of Metabase, note that for Metabase 0.38 we’ve removed the use of the PostgreSQL NonValidatingFactory for SSL validation. Upgrading from a Metabase version pre-0.38 You can see these database files from the terminal:Įxport MB_DB_CONNECTION_URI="jdbc:postgresql://localhost:5432/metabase" When the application is first launched it will attempt to create a new H2 database in the same filesystem location the application is launched from. ![]() To use the H2 database for your Metabase instance you don’t need to do anything at all. This offers a greater degree of performance and reliability when Metabase is running with many users. See Migrating from H2 to MySQL or Postgres for more details.įor production installations of Metabase we recommend that users replace the H2 database with a more robust option such as Postgres.
0 Comments
Leave a Reply. |