关于“使用 Database Migration Service 迁移到 Cloud SQL for PostgreSQL”的评价

20240731

Kamel S. · 已于 almost 2 years前审核

Eve E. · 已于 almost 2 years前审核

joice l. · 已于 almost 2 years前审核

ok

Malakari S. · 已于 almost 2 years前审核

Pablo Andres G. · 已于 almost 2 years前审核

succesfull after multiple attempts.

Garrett S. · 已于 almost 2 years前审核

Lalit S. · 已于 almost 2 years前审核

ok

Malakari S. · 已于 almost 2 years前审核

Radhish A. · 已于 almost 2 years前审核

NA

Mohit G. · 已于 almost 2 years前审核

Bruno L. · 已于 almost 2 years前审核

Anik P. · 已于 almost 2 years前审核

good lab

Paresh P. · 已于 almost 2 years前审核

Smriti V. · 已于 almost 2 years前审核

Lipsa Priyadarshini M. · 已于 almost 2 years前审核

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. · 已于 almost 2 years前审核

Pierre S. · 已于 almost 2 years前审核

Bhuvan P. · 已于 almost 2 years前审核

Alvin N. · 已于 almost 2 years前审核

Geethanjali B. · 已于 almost 2 years前审核

Sumit G. · 已于 almost 2 years前审核

bikalpa b. · 已于 almost 2 years前审核

Novita A. · 已于 almost 2 years前审核

too long though its good

CSE_Subhrajyoti B. · 已于 almost 2 years前审核

Nirajn S. · 已于 almost 2 years前审核