Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan cara mengedit instance AlloyDB untuk PostgreSQL yang ada.
Setelah membuat instance, Anda dapat mengeditnya saat sedang berjalan untuk mengubah
setelannya. Untuk mengetahui informasi tentang pengaruh setelan dan pengeditan instance terhadap instance, lihat
Melihat setelan cluster dan instance.
Untuk mengedit instance, gunakan perintah
instances update
bersama dengan konfigurasi yang ingin Anda perbarui, seperti yang ditunjukkan dalam
contoh berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[],[],null,["# Edit an instance\n\nThis page describes how to edit an existing AlloyDB for PostgreSQL instance.\n\nAfter you create an instance, you can edit it while it's running to change its\nsettings. For information about how instance settings and edits can impact an\ninstance, see\n[View cluster and instance settings](/alloydb/docs/cluster-settings?resource=primary).\n\n\nBefore you begin\n----------------\n\n- The Google Cloud project you are using must have been [enabled to access AlloyDB](/alloydb/docs/project-enable-access).\n- You must have one of these IAM roles in the Google Cloud project you are using:\n - `roles/alloydb.admin` (the AlloyDB Admin predefined IAM role)\n - `roles/owner` (the Owner basic IAM role)\n - `roles/editor` (the Editor basic IAM role)\n\n If you don't have any of these roles, contact your Organization Administrator to request\n access.\n\n\u003cbr /\u003e\n\nProcedure\n---------\n\nMost edits can be applied to an instance only when it's running. \n\n### Console\n\n1. In the Google Cloud console, go to the **Clusters** page.\n\n\n [Go to Clusters](https://console.cloud.google.com/alloydb/clusters)\n2. In the **Resource Name** column, click a cluster.\n3. On the **Overview** page, go to the **Instances in your cluster** section and find the instance that you want to edit. In the **Instance actions menu** , click **Edit**.\n4. Update any editable settings for your instance and click **Update Instance**.\n\n### gcloud\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\nTo edit an instance, use the\n[`instances update`](/sdk/gcloud/reference/alloydb/instances/update)\ncommand along with the configuration that you want to update, as shown in the\nfollowing example: \n\n```\ngcloud instances update INSTANCE_ID \\\n --region=REGION_ID \\\n --cluster=CLUSTER_ID \\\n```\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: The ID of the instance.\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: The region where the instance is placed.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: The ID of the cluster where the instance is placed.\n\nThe following example command shows how to update the number of nodes in the\nread pool: \n\n```\ngcloud alloydb instances update my-read-instance \\\n --cluster=my-cluster \\\n --region=us-central1 \\\n --read-pool-node-count=3\n```\n\nTo learn more about instance configuration flags, see\n[gcloud alloydb instances update](/sdk/gcloud/reference/alloydb/instances/update)."]]
