Bermigrasi ke Cloud SQL untuk PostgreSQL menggunakan Database Migration Service Ulasan

Simranjeet S. · Diulas 4 bulan lalu

長い。接続された、とでて進めたら接続されてないようで終了

/ 塙 敏彦 T. · Diulas 4 bulan lalu

Ajie N. · Diulas 4 bulan lalu

チェックがでない

/ 塙 敏彦 T. · Diulas 4 bulan lalu

チェックがでない

/ 塙 敏彦 T. · Diulas 4 bulan lalu

Sivakumar V. · Diulas 4 bulan lalu

Teymur O. · Diulas 4 bulan lalu

20240731

Kamel S. · Diulas 4 bulan lalu

Eve E. · Diulas 4 bulan lalu

joice l. · Diulas 4 bulan lalu

ok

Malakari S. · Diulas 4 bulan lalu

Pablo Andres G. · Diulas 4 bulan lalu

succesfull after multiple attempts.

Garrett S. · Diulas 4 bulan lalu

Lalit S. · Diulas 4 bulan lalu

ok

Malakari S. · Diulas 4 bulan lalu

Radhish A. · Diulas 4 bulan lalu

NA

Mohit G. · Diulas 4 bulan lalu

Bruno L. · Diulas 4 bulan lalu

Anik P. · Diulas 4 bulan lalu

good lab

Paresh P. · Diulas 4 bulan lalu

Smriti V. · Diulas 4 bulan lalu

Lipsa Priyadarshini M. · Diulas 4 bulan 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 4 bulan lalu

Pierre S. · Diulas 4 bulan lalu

Bhuvan P. · Diulas 4 bulan lalu