On Mon, 12 Sep 2016, Tom Lane wrote:
Hmm, AFAIK that's what it should be out of the box. Certainly on my RHEL6
machine I see
Until I make the time to upgrade this host from Slackware-14.1 to -14.2
the kernel is 3.10.17-smp.
Rich
--
Sent via pgsql-general mailing list (pgsql-general@postgr
Rich Shepard writes:
>Yes, it's a linux box. And /dev/shm/ does have incorrect permissions
> (755). Thanks to your response I remembered that chromium does not run until
> I follow its advice to chmod 1777 /dev/shm. Sure enough, chromium would not
> load.
>So, I changed the perms on /dev/s
On Mon, 12 Sep 2016, Tom Lane wrote:
A look at the code suggests this is shm_open() returning EACCES. Not sure
why that's happening. If this is a Linux box, maybe the permissions on
/dev/shm are bollixed?
Tom,
Yes, it's a linux box. And /dev/shm/ does have incorrect permissions
(755). Thank
Rich Shepard writes:
>Tried to compile 3 large programs at one time and the CPU overheated,
> shutting down the server. Now when I try to start postgres-9.5.4 (as the
> superuser, postgres) I get this result:
> postgres@salmo:~$ postgres -D /var/lib/pgsql/9.5/data/ &
> [1] 14544
> postgres@sa
Tried to compile 3 large programs at one time and the CPU overheated,
shutting down the server. Now when I try to start postgres-9.5.4 (as the
superuser, postgres) I get this result:
postgres@salmo:~$ postgres -D /var/lib/pgsql/9.5/data/ &
[1] 14544
postgres@salmo:~$ FATAL: could not open shar
