How to optimize the request to create materialized views?

Question

PostgreSQL

Good afternoon!
You need to create a materialized view, but due to the 64mb cuber limit, it constantly crashes with the error:

SQLSTATE[53100]: Disk full: 7 ERROR: could not resize shared memory segment "/PostgreSQL.1388503408" to 67244032 bytes: No space left on device

The request itself is quite large, but simple, and if you take it with a limit of 500, then the first pages are loaded, the last ones are gone. Are there any practices for creating such large views? Maybe in parts, and if so, how does it look like?

Answer 1

Set max_parallel_workers_per_gather to
0 the error is from the depths of the dynamic shared memory infrastructure for parallel query execution.

Answer 2

In general, devops found a solution for the cuber
https://stackoverflow.com/questions/46085748/defin...