Migrar para o Cloud SQL para PostgreSQL usando o Database Migration Service avaliações

subhadeep g. · Revisado há over 3 years

cloud j. · Revisado há over 3 years

Awadhesh K. · Revisado há over 3 years

rajni s. · Revisado há over 3 years

Branko T. · Revisado há over 3 years

Dung N. · Revisado há over 3 years

Juan M. · Revisado há over 3 years

Chien-hung L. · Revisado há over 3 years

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. · Revisado há over 3 years

Rishabh S. · Revisado há over 3 years

cool lab

Davide S. · Revisado há over 3 years

Davide S. · Revisado há over 3 years

Suraj G. · Revisado há over 3 years

Maksims K. · Revisado há over 3 years

Alan P. · Revisado há over 3 years

Fábio R. · Revisado há over 3 years

緒成 李. · Revisado há over 3 years

Davide S. · Revisado há over 3 years

乖乖 小. · Revisado há over 3 years

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. · Revisado há over 3 years

Ching G. · Revisado há over 3 years

Fabrizio E. · Revisado há over 3 years

Joyce H. · Revisado há over 3 years

Sushil H. · Revisado há over 3 years

偉恆 高. · Revisado há over 3 years