[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-04-03。"],[[["Database parameters for AlloyDB Omni can be configured by modifying Grand Unified Configuration (GUC) parameters in either the `postgresql.conf` file or the database cluster manifest."],["In VM environments, edit the `postgresql.conf` file to update parameters, and then reload the file for the changes to take effect, such as by restarting the Docker instance."],["On Kubernetes clusters, database parameters are managed in the `parameters` field of the `primarySpec` within the database cluster manifest, using key-value pairs for each parameter."],["Parameters that require a restart, indicated by `pg_catalog.pg_settings.context = 'postmaster'`, will automatically trigger a database restart when updated on Kubernetes clusters."],["You can view the currently applied parameters using the `kubectl get dbclusters.alloydbomni.dbadmin.goog dbcluster-sample -o jsonpath={.status.primary.currentParameters}` command, noting that discrepancies can occur if invalid parameter settings are applied."]]],[]]