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

What more would you like--I'm happy to oblige? The upgrade steps I listed
installed into a new directory, new conf file. I didn't even migrate my
(skeletal) 9.3 database. Here's the 9.5 command-line. I've attached the
referenced config file.

$ chrisr(at)ff1:~$ ps ax | grep bin/post
109999 ? S 0:00 /usr/lib/postgresql/9.5/bin/postgres -D
/var/lib/postgresql/9.5/main -c
config_file=/etc/postgresql/9.5/main/postgresql.conf

Cheers,
Chris

On Mon, Oct 10, 2016 at 5:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Chris Richards <chris(at)infinite(dot)io> writes:
> > Setting up postgresql-9.5 (9.5.4-1.pgdg14.04+2) ...
> > Creating new cluster 9.5/main ...
> > config /etc/postgresql/9.5/main
> > data /var/lib/postgresql/9.5/main
> > locale en_US.UTF-8
> > LOG: munmap(0x7fff80000000) failed: Invalid argument
> > [... snip 14 or so repeats ...]
> > LOG: munmap(0x7fff80000000) failed: Invalid argument
> > socket /var/run/postgresql
> > port 5433
> > update-alternatives: using
> > /usr/share/postgresql/9.5/man/man1/postmaster.1.gz to provide
> > /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
> > * Starting PostgreSQL 9.5 database server
> > [ OK ]
> > Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
>
> > I'm able to connect and I dumped a few default relations.
>
> > Is the munmap error of concern? It remains upon rebooting / restarting
> the
> > server.
>
> Seems pretty fishy to me; I don't know what would be causing it.
>
> [ digs in code... ] One theory is that PGSharedMemoryDetach is getting
> called more than once, but I'm not sure how that would happen. Can you
> characterize where this happens more precisely? What nondefault settings
> have you got in postgresql.conf?
>
> regards, tom lane
>