Migrate to Cloud SQL for PostgreSQL using Database Migration Service avis
24574 avis
Anik P. · Examiné il y a environ un an
good lab
Paresh P. · Examiné il y a environ un an
Smriti V. · Examiné il y a environ un an
Lipsa Priyadarshini M. · Examiné il y a environ un an
Good exercise but several errors in content. - There is no "Routes" tab in the service networking side, you have to find it through "Managed Routes". - Restricting pg configuration to the peered range in the tutorial never restarted PG service (only started due to error in shown command, and it was already running so no effect). - When you actually use the proper restart command like earlier in the tutorial when changing the config for the first time, that then breaks the later step in the tutorial to connect through Cloud Shell psql client, as now the peering range whitelist is in effect. - Data confirmation step did never confirm the assessment even though data was there, possibly because I had to re-do the migration job to a new instance as I typo'd the name. - The names could be more uniform in this sense as well (postgres vs postgresql prefixing). The pglogical setup does not conform to current Google recommendation either (in SQL statements used).
Mikael Z. · Examiné il y a environ un an
Pierre S. · Examiné il y a environ un an
Bhuvan P. · Examiné il y a environ un an
Alvin N. · Examiné il y a environ un an
Geethanjali B. · Examiné il y a environ un an
Sumit G. · Examiné il y a environ un an
bikalpa b. · Examiné il y a environ un an
Novita A. · Examiné il y a environ un an
too long though its good
CSE_Subhrajyoti B. · Examiné il y a environ un an
Nirajn S. · Examiné il y a environ un an
YASHWANT N. · Examiné il y a environ un an
フリーズで終了
/ 塙 敏彦 T. · Examiné il y a environ un an
Sayandeep P. · Examiné il y a environ un an
Paras G. · Examiné il y a environ un an
Yash G. · Examiné il y a environ un an
Good exercise but several errors in content. - There is no "Routes" tab in the service networking side, you have to find it through "Managed Routes". - Restricting pg configuration to the peered range in the tutorial never restarted PG service (only started due to error in shown command, and it was already running so no effect). - When you actually use the proper restart command like earlier in the tutorial when changing the config for the first time, that then breaks the later step in the tutorial to connect through Cloud Shell psql client, as now the peering range whitelist is in effect. - Data confirmation step did never confirm the assessment even though data was there, possibly because I had to re-do the migration job to a new instance as I typo'd the name. - The names could be more uniform in this sense as well (postgres vs postgresql prefixing). The pglogical setup does not conform to current Google recommendation either (in SQL statements used).
Mikael Z. · Examiné il y a environ un an
Krishnamoorthy T. · Examiné il y a environ un an
Lalit S. · Examiné il y a environ un an
Harsh S. · Examiné il y a environ un an
gourav d. · Examiné il y a environ un an
Anirudh K. · Examiné il y a environ un an
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.