>So it is the second part of an upgrade, Moodle updating the database, etc. The first part replacing the old software with the newer version, you have done manually. Right?
>So you have clean and running 2.9.9.
I am considering that the expression "clean" means running without errors and not clean data, ok? Yes, version 2.9.9 run clean and without errors.
>Can't move forward, neither to 3.1 nor 3.2, the error you attached appears?
> On the face of it, the ALTER TABLE hits a time out.
PHP script execution time has been increased to 300. Is there some similar configuration to increase the timeout of queries for postgres?
> How big, how many records, is the table mdl_message?
relation | total_size
mdl_logstore_standard_log | 38 GB
mdl_grade_items_history | 4952 MB
mdl_stats_daily | 2250 MB
mdl_message | 1439 MB
mdl_grade_grades_history | 1326 MB
is the fourth largest table with 1439 Mb and 457,181 lines
In the first attempt to update, moodle 2.9 to 3.0.10, the mdl_logstore_standard_log table was the problem. It is the largest table with 38 GB.
>What are your hardware resources?
moodle, moodle chat and postgree are on different VMs and I can increase capacity as needed.
-8 Gb Ram
-200 GB Storage
-16 Gb Ram
-100 GB Storage
VM Moodle Chat
-4 Gb Ram
-20 GB Storage
>Are you aware of https://docs.moodle.org/en/Administration_via_command_line#Upgrading
I know about the possibility of installing via CLI but would it be useful in that case?