amul sul <sul_a...@yahoo.co.in> writes: > When I am calling dsm_create on Linux using the POSIX DSM implementation can > succeed, but result in SIGBUS when later try to access the memory. Â This > happens because of my system does not have enough shm space & Â current > allocation in dsm_impl_posix does not allocate disk blocks.Â I wonder can > we useÂ fallocate system call (i.e. Zero-fill the file) to ensure thatÂ all > the file space has really been allocated, so that we don'tÂ later seg fault > when accessing the memory mapping. ButÂ here we will endup byÂ loop calling > âwriteâÂ squillionsÂ of times.
Wouldn't that just result in a segfault during dsm_create? I think probably what you are describing here is kernel misbehavior akin to memory overcommit. Maybe it *is* memory overcommit and can be turned off the same way. If not, you have material for a kernel bug fix/enhancement request. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers