Rich Shepard writes:
> On Fri, 30 Sep 2016, Tom Lane wrote:
>> Wrong permissions on /dev/shm, perhaps?
>Yes. I keep forgetting about this since I don't reboot this
> server/workstation often.
You ought to do some investigation and figure out what is causing
it to
On Fri, 30 Sep 2016, Tom Lane wrote:
Wrong permissions on /dev/shm, perhaps?
Tom,
Yes. I keep forgetting about this since I don't reboot this
server/workstation often.
Thanks,
Rich
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
On Fri, 30 Sep 2016, Adrian Klaver wrote:
See here:
https://www.postgresql.org/message-id/24208.1473724630%40sss.pgh.pa.us
Ah, shoot! I completely forgot about this. Yes, I reset the perms on
/dev/shm and that fixed the problem.
My apologies to all,
Rich
--
Sent via pgsql-general
On 09/30/2016 01:15 PM, Rich Shepard wrote:
> A java application threw a major error when closing and it crashed my
> system (including wiping out most of /tmp). After rebooting I su'd to user
> postgres and tried to start postgresql-9.5.4, but this error displays:
>
> postgres@salmo:~$ FATAL:
Rich Shepard writes:
>A java application threw a major error when closing and it crashed my
> system (including wiping out most of /tmp). After rebooting I su'd to user
> postgres and tried to start postgresql-9.5.4, but this error displays:
> postgres@salmo:~$
On 09/30/2016 01:15 PM, Rich Shepard wrote:
A java application threw a major error when closing and it crashed my
system (including wiping out most of /tmp). After rebooting I su'd to user
postgres and tried to start postgresql-9.5.4, but this error displays:
postgres@salmo:~$ FATAL: could
A java application threw a major error when closing and it crashed my
system (including wiping out most of /tmp). After rebooting I su'd to user
postgres and tried to start postgresql-9.5.4, but this error displays:
postgres@salmo:~$ FATAL: could not open shared memory segment