Also hitting this migration issue, it’s using only a single core and only at most 30 of the available 96 GB of memory, so it doesn’t seem to be a resource limitation. Is there any way for me to try and increase the psql command timeout?
edit: Managed to bump the timeout to 1 hour and waited…. this time it took ~5400 seconds (that’s way more than an hour) and still did not manage to complete….
edit2: saw that the wsl memory limit was (by default) set to 50% of system mem, and seeing a significant increase in disk usage (probably swapping like crazy) the moment that limit was hit, I decided to try and increwase the mem limit in wsl as well; set it to 71GB/66GiB and it still hits the limit, it just takes ~30 minutes; still swapping like crazy and still way longer than the default 10 minutes… I need to check if they are doing the entire set of migration scripts in one transaction or something… That would probably mean that when it fails the next run has to start from scratch again…