[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-18 (世界標準時間)。"],[[["\u003cp\u003eAlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database service designed for demanding enterprise workloads, offering superior performance, scale, and availability.\u003c/p\u003e\n"],["\u003cp\u003eAlloyDB offers various connectivity options, including private IP addresses, cloud-hosted TCP proxy, VPC peering, and reverse SSH tunnel, with SSL/TLS available for securing network connections.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating an AlloyDB cluster, users can customize various configuration settings to meet their specific needs, as detailed in the documentation.\u003c/p\u003e\n"],["\u003cp\u003eNew AlloyDB clusters are initially accessed using the \u003ccode\u003epostgres\u003c/code\u003e account, but users are restricted from having \u003ccode\u003eSUPER\u003c/code\u003e privileges due to its managed service nature.\u003c/p\u003e\n"],["\u003cp\u003eAlloyDB instances are configured for high availability by default, enhancing reliability.\u003c/p\u003e\n"]]],[],null,["# AlloyDB for PostgreSQL\n\nOverview\n--------\n\nAlloyDB for PostgreSQL is a fully managed PostgreSQL-compatible database service for your most demanding enterprise database workloads. AlloyDB combines the best of Google Cloud with one of the most popular open-source database engines, PostgreSQL, for superior performance, scale, and availability. For information specific to AlloyDB for PostgreSQL, see the\n[AlloyDB for PostgreSQL documentation](/alloydb/docs).\n\nFeatures\n--------\n\nIf you're new to AlloyDB for PostgreSQL, then be sure to check out the\n[AlloyDB for PostgreSQL features](/alloydb#all-features) page.\n\nInstance settings\n-----------------\n\nMany configuration settings go into the creation of a AlloyDB cluster.\nYour needs may vary from the defaults.\nSee the [Create a cluster and its primary instance](/alloydb/docs/cluster-create) page for more information.\n\nConnectivity\n------------\n\nAlloyDB for PostgreSQL offers [connectivity](/alloydb/docs/configure-connectivity) through private IP addresses.\n\nIn cases where you are migrating from a Cloud SQL for PostgreSQL source that is using the old Cloud SQL producer network architecture, and in several [other scenarios](/database-migration/docs/postgresql-to-alloydb/networking-methods#common_connectivity_scenarios_and_solutions), the recommended connectivity method is a [cloud-hosted TCP proxy](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-tcp-proxy-via-cloud-hosted-vm). Database Migration Service can provide a guided experience to help you set this up.\n\n[VPC peering](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-vpc-peering)\nconnectivity method is applicable to self-managed sources in Google Cloud, and to sources in other cloud platforms that are connected to your Google Cloud VPC via VPN or Interconnect. [Reverse SSH tunnel](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-reverse-ssh-tunnel) is also offered for scenarios where using unsecure connections are required.\n\nIn all cases, SSL/TLS can also be used to secure the underlying network connection between the source and destination databases.\n\nAlloyDB users\n-------------\n\nThe first time you connect to a new AlloyDB cluster, use the\n`postgres` account.\n\nBecause it's a managed service, AlloyDB doesn't allow PostgreSQL users to have\n`SUPER` privileges.\n\nHigh availability\n-----------------\n\nAlloyDB instances are [high availability (HA)](/sql/docs/postgres/high-availability) by default.\n\nWhat's next\n-----------\n\nLearn more about [everything you can do](/alloydb/docs/overview)\nwith your AlloyDB instance."]]