# PG throws could not resize shared memory segment 错误

**URL:** https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744
**Category:** Self-hosting
**Created:** [2018年四月6日 16:52 UTC](https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744 "2018-04-06T16:52:20Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Gunnar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gunnar/32/119647_2.png) [@Gunnar](https://meta.discourse.org/u/Gunnar)
#### Post date: [2018年四月6日 18:37 UTC](https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744/5 "2018-04-06T18:37:33Z")

</div>

> [@supermathie](#):
>
> You should raise the limit when launching the postgres container by including the --shm-size=1g parameter.
> 
> We’ll look at fixing this in the launcher.
> 
> (or as the link suggests, disable parallelism in pg10 with max\_parallel\_workers\_per\_gather = 0)

Thanks. How would I do either of those? I searched, found this post ([Starting Discourse on a Specific Docker Network - #3 by dlynch158](https://meta.discourse.org/t/starting-discourse-on-a-specific-docker-network/49401/3)) and following the example added the following line to my app.yml:

`docker_args: "--shm-size=1g"`

Then ran launcher rebuild app. That didn’t make any difference though, shm is still 64M inside the container.

Thanks,  
Gunnar

---

_[View the full topic](https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744)._