PostgreSQL용 AlloyDB는 가장 까다로운 엔터프라이즈 데이터베이스 워크로드를 위한 완전 관리형 PostgreSQL 호환 데이터베이스 서비스입니다. AlloyDB는 뛰어난 성능, 확장성, 가용성을 위해 가장 인기 있는 오픈소스 데이터베이스 엔진 중 하나인 PostgreSQL과 Google Cloud 의 장점을 결합합니다. PostgreSQL용 AlloyDB에 관한 자세한 내용은 PostgreSQL용 AlloyDB 문서를 참고하세요.
기존 Cloud SQL 프로듀서 네트워크 아키텍처를 사용하는 PostgreSQL용 Cloud SQL 소스에서 마이그레이션하는 경우와 몇 가지 기타 시나리오에서는 클라우드 호스팅 TCP 프록시를 사용하는 것이 좋습니다. Database Migration Service에서는 이를 설정하는 데 도움이 되는 안내 환경을 제공할 수 있습니다.
VPC 피어링 연결 방법은 Google Cloud의 자체 관리 소스와 VPN 또는 Interconnect를 통해 Google Cloud VPC에 연결된 다른 클라우드 플랫폼의 소스에 적용할 수 있습니다. 안전하지 않은 연결을 사용해야 하는 시나리오에도 역방향 SSH 터널이 제공됩니다.
모든 경우에 SSL/TLS를 사용하여 소스 데이터베이스와 대상 데이터베이스 간의 기본 네트워크 연결을 보호할 수도 있습니다.
AlloyDB 사용자
새 AlloyDB 클러스터에 처음 연결할 때는 postgres 계정을 사용하세요.
관리형 서비스이므로 AlloyDB는 PostgreSQL 사용자가 SUPER 권한을 갖도록 허용하지 않습니다.
[[["이해하기 쉬움","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-09-03(UTC)"],[[["\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."]]
