# PG throws error de no poder redimensionar segmento de memoria compartida

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

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [6 Abril, 2018 18:40 UTC](https://meta.discourse.org/t/pg-throws-could-not-resize-shared-memory-segment-error/84744/6 "2018-04-06T18:40:23Z")

</div>

You need to make sure that’s on your data container.

EDIT:

OK, adding the following:

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

```

to your `app.yml` (if all-in-one) or `data.yml` (if separate pg) containers should prevent this from happening. I’ve left the shm size at a conservative 512MB.

Or if you pull latest and relaunch it’ll now start the container with that shm size.

@tgxworld I’ve pushed a change that changes the launcher to always launch with 512MB SHM size under bootstrap or run. Should be safe.

---

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