Re: LOG: munmap(0x7fff80000000) failed: Invalid argument

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Richards <chris(at)infinite(dot)io>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: LOG: munmap(0x7fff80000000) failed: Invalid argument
Date: 2016-10-11 23:15:55
Message-ID: 29595.1476227755@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Richards <chris(at)infinite(dot)io> writes:
> Oh the email spam :P

No problem. I'm starting to think that this isn't actually a Postgres
bug, but rather something funny with your kernel. The code in sysv_shmem
is certainly as fragile as can be, but I'm darned if I can find an
existing code path that would actually break it --- and the lack of other
complaints is pointing towards something funny with your system, too.

First off, does changing "huge_pages" in postgresql.conf alter the
behavior? (It defaults to "try", see what happens with "on" or "off".)

Second, I notice that you've got

> Hugepagesize: 1048576 kB

which is just enormous. PG is only going to request circa 140MB given
the settings you mentioned. We've seen reports of kernel bugs that cause
mmap() to fail for requests that aren't a multiple of the hugepage size,
but I've not heard that mmap() might succeed and then munmap() fail.
That seems like what's happening to you though.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2016-10-12 00:39:52 Re: BDR: changing dsn on a running node
Previous Message Jason Dusek 2016-10-11 20:13:31 Re: SERIALIZABLE and INSERTs with multiple VALUES