| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, amul sul <sul_amul(at)yahoo(dot)co(dot)in>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create(). |
| Date: | 2017-09-25 18:56:34 |
| Message-ID: | 2034.1506365794@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Hmm, so I tested this patch on my RHEL6 box (kernel 2.6.32) and it
> immediately fell over with
> 2017-09-25 14:23:48.410 EDT [325] FATAL: could not resize shared memory segment "/PostgreSQL.1682054886" to 6928 bytes: Operation not supported
> during startup. I wonder whether we need to round off the request.
Nope, rounding off doesn't help. What does help is using posix_fallocate
instead. I surmise that glibc knows something we don't about how to call
fallocate(2) successfully on this kernel version.
Rather than dig into the guts of glibc to find that out, though, I think
we should just s/fallocate/posix_fallocate/g on this patch. The argument
for using the former seemed pretty thin to begin with.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jignesh Shah | 2017-09-25 19:08:19 | Re: Built-in plugin for logical decoding output |
| Previous Message | Oliver Ford | 2017-09-25 18:52:19 | Re: Fix number skipping in to_number |