There is a case that some Canada large Uni clients (York) have hit where the task that generates the status report is running out of memory when building a CTE.
In this case the problem is that MySQL (in theory that same could happen for PG) is creating a TEMP TABLE (in RAM) behind the scenes and running out a memory and failing as the record set is too much.
We have proposed a solution (not the default) where instead of creating the CTE we populate an actual report table (which gets purged after each report) so that the DB doesn't hit the same memory constraints.
See https://wrms.catalyst.net.nz/wr.php?request_id=493098
There is a case that some Canada large Uni clients (York) have hit where the task that generates the status report is running out of memory when building a CTE.
In this case the problem is that MySQL (in theory that same could happen for PG) is creating a TEMP TABLE (in RAM) behind the scenes and running out a memory and failing as the record set is too much.
We have proposed a solution (not the default) where instead of creating the CTE we populate an actual report table (which gets purged after each report) so that the DB doesn't hit the same memory constraints.
See https://wrms.catalyst.net.nz/wr.php?request_id=493098