关于“使用 Database Migration Service 迁移到 Cloud SQL for PostgreSQL”的评价

Good

Om K. · 已于 about 1 year前审核

nice

Sparsh M. · 已于 about 1 year前审核

Daryl M. · 已于 about 1 year前审核

Colin D. · 已于 about 1 year前审核

This lab takes way too much time to take the password when i connect to postgresql

proximity b. · 已于 about 1 year前审核

Gorla Sai Praneeth R. · 已于 about 1 year前审核

piyush t. · 已于 about 1 year前审核

Vipin D. · 已于 about 1 year前审核

Ankur G. · 已于 about 1 year前审核

Abhineet K. · 已于 about 1 year前审核

good

Sravani V. · 已于 about 1 year前审核

Chaitanya T. · 已于 about 1 year前审核

ENUGANDHULA N. · 已于 about 1 year前审核

VINIT P. · 已于 about 1 year前审核

Ananda S. · 已于 about 1 year前审核

Pranav P. · 已于 about 1 year前审核

Nandini J. · 已于 about 1 year前审核

Urshita M. · 已于 about 1 year前审核

PRIYADEEP M. · 已于 about 1 year前审核

Instructions are invalid for this section. The Imported routes tab does not exist... Allow access to the postgresql-vm instance from automatically allocated IP range In this step you will edit the pg_hba.conf PostgreSQL configuration file to allow the Database Migration Service to access the stand-alone PostgreSQL database. Get the allocated IP address range. In the Google Cloud Console on the Navigation menu (Navigation menu icon), right-click VPC network > VPC network peering and open it in a new tab. Click on the servicenetworking-googleapis-com entry. In the Imported routes tab, select and copy the Destination IP range (e.g. 10.107.176.0/24).

Michael M. · 已于 about 1 year前审核

Anamithra K. · 已于 about 1 year前审核

Saurabh s. · 已于 about 1 year前审核

Shayan M. · 已于 about 1 year前审核

good

Vedant P. · 已于 about 1 year前审核

mafyul i. · 已于 about 1 year前审核