Bermigrasi ke Cloud SQL untuk PostgreSQL menggunakan Database Migration Service Ulasan
24454 ulasan
Anik P. · Diulas sekitar 1 tahun lalu
good lab
Paresh P. · Diulas sekitar 1 tahun lalu
Smriti V. · Diulas sekitar 1 tahun lalu
Lipsa Priyadarshini M. · Diulas sekitar 1 tahun lalu
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. · Diulas sekitar 1 tahun lalu
Pierre S. · Diulas sekitar 1 tahun lalu
Bhuvan P. · Diulas sekitar 1 tahun lalu
Alvin N. · Diulas sekitar 1 tahun lalu
Geethanjali B. · Diulas sekitar 1 tahun lalu
Sumit G. · Diulas sekitar 1 tahun lalu
bikalpa b. · Diulas sekitar 1 tahun lalu
Novita A. · Diulas sekitar 1 tahun lalu
too long though its good
CSE_Subhrajyoti B. · Diulas sekitar 1 tahun lalu
Nirajn S. · Diulas sekitar 1 tahun lalu
YASHWANT N. · Diulas sekitar 1 tahun lalu
フリーズで終了
/ 塙 敏彦 T. · Diulas sekitar 1 tahun lalu
Sayandeep P. · Diulas sekitar 1 tahun lalu
Paras G. · Diulas sekitar 1 tahun lalu
Yash G. · Diulas sekitar 1 tahun lalu
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. · Diulas sekitar 1 tahun lalu
Krishnamoorthy T. · Diulas sekitar 1 tahun lalu
Lalit S. · Diulas sekitar 1 tahun lalu
Harsh S. · Diulas sekitar 1 tahun lalu
gourav d. · Diulas sekitar 1 tahun lalu
Anirudh K. · Diulas sekitar 1 tahun lalu
Kami tidak dapat memastikan bahwa ulasan yang dipublikasikan berasal dari konsumen yang telah membeli atau menggunakan produk terkait. Ulasan tidak diverifikasi oleh Google.