| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | reiner peterke <zedaardv(at)drizzle(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Problems with huge_pages and IBM Power8 |
| Date: | 2016-04-12 20:41:35 |
| Message-ID: | 20687.1460493695@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
reiner peterke <zedaardv(at)drizzle(dot)com> writes:
>> On Apr 12, 2016, at 10:20 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> I've a bit of a hard time believing that this is related to huge pages.
> Well all i have at the moment is that when we disabled huge pages on the kernel level and then restarted postgres there were no additional crashes.
That log excerpt shows pretty conclusively that both your semaphores and
your shared memory were yanked out from under you. That's not a Postgres
bug, and it seems unlikely to be related to huge pages either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-04-12 20:48:49 | Re: raw output from copy |
| Previous Message | reiner peterke | 2016-04-12 20:35:12 | Re: Problems with huge_pages and IBM Power8 |