Migrar para o Cloud SQL para PostgreSQL usando o Database Migration Service avaliações
24452 avaliações
Smriti V. · Revisado há about 1 year
Lipsa Priyadarshini M. · Revisado há about 1 year
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. · Revisado há about 1 year
Pierre S. · Revisado há about 1 year
Bhuvan P. · Revisado há about 1 year
Alvin N. · Revisado há about 1 year
Geethanjali B. · Revisado há about 1 year
Sumit G. · Revisado há about 1 year
bikalpa b. · Revisado há about 1 year
Novita A. · Revisado há about 1 year
too long though its good
CSE_Subhrajyoti B. · Revisado há about 1 year
Nirajn S. · Revisado há about 1 year
YASHWANT N. · Revisado há about 1 year
フリーズで終了
/ 塙 敏彦 T. · Revisado há about 1 year
Sayandeep P. · Revisado há about 1 year
Paras G. · Revisado há about 1 year
Yash G. · Revisado há about 1 year
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. · Revisado há about 1 year
Krishnamoorthy T. · Revisado há about 1 year
Lalit S. · Revisado há about 1 year
Harsh S. · Revisado há about 1 year
gourav d. · Revisado há about 1 year
Anirudh K. · Revisado há about 1 year
Jacob V. · Revisado há about 1 year
Gourav D. · Revisado há about 1 year
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.