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

ok

Malakari S. · Sprawdzono około rok temu

Radhish A. · Sprawdzono około rok temu

NA

Mohit G. · Sprawdzono około rok temu

Bruno L. · Sprawdzono około rok temu

Anik P. · Sprawdzono około rok temu

good lab

Paresh P. · Sprawdzono około rok temu

Smriti V. · Sprawdzono około rok temu

Lipsa Priyadarshini M. · Sprawdzono około 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 około rok temu

Pierre S. · Sprawdzono około rok temu

Bhuvan P. · Sprawdzono około rok temu

Alvin N. · Sprawdzono około rok temu

Geethanjali B. · Sprawdzono około rok temu

Sumit G. · Sprawdzono około rok temu

bikalpa b. · Sprawdzono około rok temu

Novita A. · Sprawdzono około rok temu

too long though its good

CSE_Subhrajyoti B. · Sprawdzono około rok temu

Nirajn S. · Sprawdzono około rok temu

YASHWANT N. · Sprawdzono około rok temu

フリーズで終了

/ 塙 敏彦 T. · Sprawdzono około rok temu

Sayandeep P. · Sprawdzono około rok temu

Paras G. · Sprawdzono około rok temu

Yash G. · Sprawdzono około 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 około rok temu

Krishnamoorthy T. · Sprawdzono około rok temu