> On Mar 6, 2020, at 8:34 AM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > > Oh, if it's trying to resize then this is dynamic shared memory, not > the small static block. On most platforms we use POSIX shm_open() for > that purpose, not SysV-style shm ... what have you got > dynamic_shared_memory_type set to? I just confirmed that it is POSIX. (I'm pretty sure we've never even considered changing the default.) So it would seem that, in this context at least, the limit applies to it. And the context is containerized, Kubernetes, where there is no option to set the container's shm limit so we just have to use the shm mount trick. > It could be that the space limit applies to both APIs anyway, in which > case your choices are to raise the limit or disable parallel query. Well if it's coming from parallel query then I'm OK with the workaround. Primarily I wanted to make sure it wasn't caused by something dumb/worthless that we should just not do. (For instance, for historical reasons, we are temporarily running with max_connections way higher than is good practice...)
