Migrate to Cloud SQL for PostgreSQL Using Database Migration Service Reviews

rajni s. · Reviewed over 3 years ago

Branko T. · Reviewed over 3 years ago

Dung N. · Reviewed over 3 years ago

Juan M. · Reviewed over 3 years ago

Chien-hung L. · Reviewed over 3 years ago

There is an error after you've done this task "Allow access to the posgresql-vm instance from automatically allocated IP range". You can't connect to your standalone database server in postgresql-vm again because you've changed "allow access to all hosts" setting in "/etc/postgresql/13/main/pg_hba.conf". I've resolved this by changed again the value to 0.0.0.0/0 again. Also do not use "--quiet" in this command: "gcloud sql connect postgresql-cloudsql --user=postgres --quiet", if you have set your project ID to your cloudshell. This makes the popup that asks you to authorize the access not showed up.

Rizki R. · Reviewed over 3 years ago

Rishabh S. · Reviewed over 3 years ago

cool lab

Davide S. · Reviewed over 3 years ago

Davide S. · Reviewed over 3 years ago

Suraj G. · Reviewed over 3 years ago

Maksims K. · Reviewed over 3 years ago

Alan P. · Reviewed over 3 years ago

Fábio R. · Reviewed over 3 years ago

緒成 李. · Reviewed over 3 years ago

Davide S. · Reviewed over 3 years ago

乖乖 小. · Reviewed over 3 years ago

In the process when I practice labs, I test vpc peering and test failed three times. I am too impatient to test until success , I delete Task2 all step I do . I want to do again but it's not working and still test more than 5 times. Even I do all Task4 & Task5 step ,"Check" cannot detect.

TINGYU Y. · Reviewed over 3 years ago

Ching G. · Reviewed over 3 years ago

Fabrizio E. · Reviewed over 3 years ago

Joyce H. · Reviewed over 3 years ago

Sushil H. · Reviewed over 3 years ago

偉恆 高. · Reviewed over 3 years ago

奕心 陳. · Reviewed over 3 years ago

Pui Wa L. · Reviewed over 3 years ago

小瑋 G. · Reviewed over 3 years ago