stack depth limit exceeded

Hi TaariqMegaC 

PostgreSQL has a configuration parameter called max_stack_depth, which specifies the maximum safe depth of the server's execution stack. The default value is set to 2MB. If your queries are complex, they may exceed this limit, especially if they involve deep recursion or nested subqueries.

If your dataflow includes complex queries, particularly those involving nested updates or deep recursion, this could lead to the stack depth error. A contrived query can cause unreasonable amounts of time spent trying to flatten subqueries, which may not only lead to performance issues but also trigger the stack depth limit.

As a potential workaround, you can increase the max_stack_depth parameter within a session if you have superuser access. This adjustment may temporarily resolve the issue but should be done cautiously, ensuring that it does not adversely affect the overall performance of the database.
SET max_stack_depth = '4MB'; -- Example value, adjust as needed

Consider whether any recent changes to the database schema or query design have introduced complexity. This could include new joins, additional calculated fields, or modifications in how data is being retrieved.

Performance-related issues, such as high load on the database server or resource throttling, can also contribute to this error. Monitoring the performance metrics can provide insights into whether resource limits are being exceeded.

If the error began occurring after a specific date, such as October 4th in your case, it may be worthwhile to investigate any changes made around that time, including updates to PostgreSQL itself or any changes in the data sources being queried