关于“使用資料庫移轉服務，遷移至 PostgreSQL 適用的 Cloud SQL”的评价

Simranjeet S. · 评论4 months之前

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

/ 塙 敏彦 T. · 评论4 months之前

Ajie N. · 评论4 months之前

チェックがでない

/ 塙 敏彦 T. · 评论4 months之前

チェックがでない

/ 塙 敏彦 T. · 评论4 months之前

Sivakumar V. · 评论4 months之前

Teymur O. · 评论4 months之前

20240731

Kamel S. · 评论4 months之前

Eve E. · 评论4 months之前

joice l. · 评论4 months之前

ok

Malakari S. · 评论4 months之前

Pablo Andres G. · 评论4 months之前

succesfull after multiple attempts.

Garrett S. · 评论4 months之前

Lalit S. · 评论4 months之前

ok

Malakari S. · 评论4 months之前

Radhish A. · 评论4 months之前

NA

Mohit G. · 评论4 months之前

Bruno L. · 评论4 months之前

Anik P. · 评论4 months之前

good lab

Paresh P. · 评论4 months之前

Smriti V. · 评论4 months之前

Lipsa Priyadarshini M. · 评论4 months之前

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. · 评论4 months之前

Pierre S. · 评论4 months之前

Bhuvan P. · 评论4 months之前