# PG throws could not resize shared memory segment error

**URL:** <https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744>\
**Category:** Self-hosting\
**Created:** [April 6, 2018, 4:52pm 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:** 7

<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:** [April 6, 2018, 8:53pm UTC](https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744/7 "2018-04-06T20:53:59Z")

</div>

Thanks for adding that to launcher, shm is now 512m inside our container (and yes, we have just the one).

Just FYI, for some reason, adding the

`docker_args: "--shm-size=512m"`

line to app.yml (and rebuilding) did nothing.

Thanks!  
Gunnar

---

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