Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

32-bit OS Support #116

Open
wrightleft opened this issue Jan 30, 2023 · 1 comment
Open

32-bit OS Support #116

wrightleft opened this issue Jan 30, 2023 · 1 comment

Comments

@wrightleft
Copy link

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
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant