Setting plannedconcurrency and maxconcurrency to 1 isn't really a good solution, except maybe for a resource pool that is only using a small percentage of the overall memory.
Better to make sure that you're following best practices regarding statistics and joins involving larger tables.
See this thread for some existing discussion on this topic:
Answers
If you don't need to consider the concurrency, please try to run that query with concurrency = 1;
If you still hit the same error, you may need to do the query optimization to reduce the necessary memory.
https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AnalyzingData/Optimizations/OptimizingQueryPerformance.htm
Hi Hibiki
Thank you for your support. I will try it.
Setting plannedconcurrency and maxconcurrency to 1 isn't really a good solution, except maybe for a resource pool that is only using a small percentage of the overall memory.
Better to make sure that you're following best practices regarding statistics and joins involving larger tables.
See this thread for some existing discussion on this topic:
https://forum.vertica.com/discussion/238537/question-about-error-join-inner-did-not-fit-in-memory