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

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. · 评论over 1 year之前

Pierre S. · 评论over 1 year之前

Bhuvan P. · 评论over 1 year之前

Alvin N. · 评论over 1 year之前

Geethanjali B. · 评论over 1 year之前

Sumit G. · 评论over 1 year之前

bikalpa b. · 评论over 1 year之前

Novita A. · 评论over 1 year之前

too long though its good

CSE_Subhrajyoti B. · 评论over 1 year之前

Nirajn S. · 评论over 1 year之前

YASHWANT N. · 评论over 1 year之前

フリーズで終了

/ 塙 敏彦 T. · 评论over 1 year之前

Sayandeep P. · 评论over 1 year之前

Paras G. · 评论over 1 year之前

Yash G. · 评论over 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. · 评论over 1 year之前

Krishnamoorthy T. · 评论over 1 year之前

Lalit S. · 评论over 1 year之前

Harsh S. · 评论over 1 year之前

gourav d. · 评论over 1 year之前

Anirudh K. · 评论over 1 year之前

Jacob V. · 评论over 1 year之前

Gourav D. · 评论over 1 year之前

Megha K. · 评论over 1 year之前

Ayush S. · 评论over 1 year之前