| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Willy-Bas Loos <willybas(at)gmail(dot)com>, lst_hoe02(at)kwsoft(dot)de, pgsql-admin <pgsql-admin(at)postgresql(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] openvz and shared memory trouble |
| Date: | 2014-03-31 15:28:13 |
| Message-ID: | 16649.1396279693@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> At this point the memory allocation as a problem is as much conjecture
> as anything else, at least to me. So what is causing SIGBUS is an open
> question in my mind.
Agreed, it's unproven what's causing the SIGBUS in the case at hand.
However, in the case I investigated for Josh Kupershmidt, it was provably
the fault of the kernel for failing to supply memory to back the shared
memory segment that it had previously agreed to allocate. The fact that
both users are trying to run their standby server under OpenVZ is, shall
we say, merely suggestive.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-03-31 19:21:03 | Re: [ADMIN]openvz and shared memory trouble |
| Previous Message | Adrian Klaver | 2014-03-31 15:14:36 | Re: [ADMIN]openvz and shared memory trouble |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2014-03-31 15:48:01 | Re: char array overhead |
| Previous Message | Adrian Klaver | 2014-03-31 15:14:36 | Re: [ADMIN]openvz and shared memory trouble |