Yes, it's a VPS running FreeBSD 6.1, so presumably it's in a FreeBSD
jail. I'll verify that with my hosting provider and probably follow up
along these lines.
http://www.postgresql.org/docs/8.1/interactive/kernel-resources.html
seems to recommend running as different uid's as well. Right now it's r
"Wes Sheldahl" <[EMAIL PROTECTED]> writes:
> I seem to have an unstable/unreliable installation of postgresql, and I'm
> not sure how to troubleshoot it.
> Symptoms:
> $ psql postgres
> psql: FATAL: semctl(851974, 3, SETVAL, 0) failed: Invalid argument
AFAICS the only documented reason for that s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Are you running this in a FreeBSD jail under 6.1? It sounds like the problem
that I had where a second postmaster starts up and stomp's on the previous
postgresql's shared memory ...
To "fix", you have to make sure that both instances run as diffe
