Postgres /dev/shm too small — pgvector falling back to brute-force
intelagentstudios
HOBBYOP

25 days ago

Hi — running into a /dev/shm sizing issue on a managed Postgres service.

Project: platform (118a1bee-e262-4166-8c49-ecf4b7b7f378)

Service: Postgres (093478ec-d920-4f18-8f55-41fedd5362b9)

Image: pgvector/pgvector:pg16

Region: EU West (Amsterdam)

Logs are filled with:

could not resize shared memory segment "/PostgreSQL.*" to 63999968 bytes: No space left on device

The container's /dev/shm appears to be the Docker default (64MB), so Postgres can't allocate the ~65MB it

needs for parallel-query shared memory. As a result pgvector keeps falling back to brute-force search, which

is slowing every knowledge-grid operation in our app.

Could you bump --shm-size on this container to 256MB (or larger if available on our plan)? Happy to apply any

client-side workaround in the meantime, but the proper fix is at the container level.

Thanks

1 Replies

25 days ago

(no markdown available for this content)


Welcome!

Sign in to your Railway account to join the conversation.

Loading...