Running scripts manually can lead to unintended consequences. Certainly not to be done in production instances.
The 2.32 upgrade is a major database upgrade which takes about 7-10 minutes on a db of size similar to demo dbs.
We need to set the max_locks_per_transaction to atleast 100 in postgres.conf and restart the postgres server for the change to take effect and then deploy 2.32war.
To confirm whether a conf change has taken effect, after pg server restart you can execute
select setting,pending_restart from pg_settings where name= 'max_locks_per_transaction';
The setting column should be the new setting value you changed to (100 in this case), and pending_restart column should have a value of false.