IBM Cloud® Hyper Protect DBaaS for PostgreSQL now supports changing some of the PostgreSQL configuration settings so you can tune your PostgreSQL databases to your use case.
Currently, the available configuration settings are as follows:
- shared_buffers: Shared memory buffers that the server use. The recommended memory allocation for shared_buffers is 1/4 of the service instance’s RAM.
- max_locks_per_transaction: The setting controls the average number of object locks allocated for each transaction. Increase it only if you have queries that touch many different tables in a single transaction.
- deadlock_timeout: The number of milliseconds to wait before checking for deadlock and the duration where lock waits are logged. Setting this number too low negatively impacts performance.
You can use the Hyper Protect DBaaS CLI or API to change the configuration. If the request to change configuration settings fails, the Hyper Protect DBaaS for PostgreSQL SRE team will be notified automatically. You can also use the CLI commands or API requests to view the change request status.
For more information and detailed instructions, see Changing the PostgreSQL configuration.
More about IBM Cloud Hyper Protect DBaaS
IBM Cloud Hyper Protect DBaaS offers a highly secure and managed databases — including PostgreSQL and MongoDB Enterprise Server — and provides a high level of data confidentiality for your sensitive data in the IBM Cloud.
Go to the IBM Cloud Catalog to try out the 30-day free plan for Hyper Protect DBaaS. You can choose between two database options:
Check out the Getting Started with IBM Cloud Hyper Protect DBaaS and Bring Your Own Key to IBM Cloud Hyper Protect DBaaS videos in the IBM Demos Collection.
Consult the Hyper Protect DBaaS for PostgreSQL documentation or the Hyper Protect DBaaS for MongoDB documentation for details on how to get started.