On May 23, 2006, at 1:31 PM, Kirk Strauser wrote:
I just upgraded from 6-STABLE as of 2006-02-18 to 6-STABLE as of
2006-05-21,
and was surprised to find that PostgreSQL wouldn't start because it
couldn't allocate enough shared memory. Thing is, I didn't make a
single
hardware change during the reboot and didn't upgrade any ports on the
machine.
My emergency fix was to edit postgresql.conf to change
shared_buffers from
8192 to 2048. Unfortunately, that seems to be hurting performance
- I'm
getting annoying deadlocks at 4AM whenever multiple daemons start
their
overnight batch runs.
Has anyone else seen this behavior when upgrading from 6.0 to 6.1?
Any
ideas for a fix?
I apologize for not having a logfiles, but I was pretty much in a
panic to
get it back up and running ASAP and didn't think about it until it
was too
late.
--
Kirk Strauser
You need to adjust the shared memory segments allowed by the kernel; see
/usr/ports/databases/postgresql<your-version>-server/pkg-message-
server for
what to add to your kernel config. Most likely, you forgot to move
over your
kernel customizations to your new kernel...?
-Marshall
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
