32-bit OS Support

[wrightleft]

The numbers produced by timescaledb-tune for my 32-bit OS caused postgresql to crash due to memory allocation issues.

FATAL:  could not map anonymous shared memory: Cannot allocate memory
HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 4292468736 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.

It would be nice if timescaledb-tune could detect aspects of the OS, such as being 32-bit, and didn't provide numbers that immediately make postgresql crash.

[wrightleft]

See also -> http://rhaas.blogspot.com/2011/05/sharedbuffers-on-32-bit-systems.html