DB_shared_buffers（総RAMの0.1%）とDB_work_mem（総RAMの0.03%）を増やせません

[markersocial]

@pfaffman

Refers to the hard drive space, not the ram.

Thanks @pfaffman - I thought that too initially, but then I read this thread:

PG throws could not resize shared memory segment error

After upgrading (with ‘launcher rebuild app’ times two) to Postgres 10, we’ve started seeing errors like this in /logs: Failed to handle exception in exception app middleware : PG::DiskFull: ERROR: could not resize shared memory segment "/PostgreSQL.682207201" to 283432 bytes: No space left on device : SELECT "topics"."id" AS t0_r0, "topics"."title" AS t0_r1, "topics"."last_posted_at" AS t0_r2, … Ideas? Looks like PG is unable to increase the size of a shared memory segment, can this be tuned …

There is a lot of free space also