Opinie (Migrate to Cloud SQL for PostgreSQL Using Database Migration Service)

Smriti V. · Sprawdzono ponad rok temu

Lipsa Priyadarshini M. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Pierre S. · Sprawdzono ponad rok temu

Bhuvan P. · Sprawdzono ponad rok temu

Alvin N. · Sprawdzono ponad rok temu

Geethanjali B. · Sprawdzono ponad rok temu

Sumit G. · Sprawdzono ponad rok temu

bikalpa b. · Sprawdzono ponad rok temu

Novita A. · Sprawdzono ponad rok temu

too long though its good

CSE_Subhrajyoti B. · Sprawdzono ponad rok temu

Nirajn S. · Sprawdzono ponad rok temu

YASHWANT N. · Sprawdzono ponad rok temu

フリーズで終了

/ 塙 敏彦 T. · Sprawdzono ponad rok temu

Sayandeep P. · Sprawdzono ponad rok temu

Paras G. · Sprawdzono ponad rok temu

Yash G. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Krishnamoorthy T. · Sprawdzono ponad rok temu

Lalit S. · Sprawdzono ponad rok temu

Harsh S. · Sprawdzono ponad rok temu

gourav d. · Sprawdzono ponad rok temu

Anirudh K. · Sprawdzono ponad rok temu

Jacob V. · Sprawdzono ponad rok temu

Gourav D. · Sprawdzono ponad rok temu