Re: Shared memory corrupted?

Tom Lane wrote:

>Jeff Boes <jboes(at)nexcerpt(dot)com> writes:
>
>
>>We are experiencing the following error, usually during our nightly
>>delete-and-vacuum cycle (when there are very few other connections to
>>the database):
>>
>>
>
>
>
>>2003-10-30 01:36:59 [25392] LOG: server process (pid 697) was
>>terminated by signal 14
>>
>>
>
>What's signal 14 on your machine? (Look in /usr/include/signal.h to
>be sure.) Also, what PG version is this?
>
> regards, tom lane
>
>

signal.h doesn't have any definitions for signal numbers in it; "kill
-l" lists 14 as:

14) SIGALRM

This is Pg 7.3.4, running on Linux 7.3 (Kernel 2.4.18-18.7.xsmp on a
2-processor i686).

The system has 4 GB of RAM. Shared memory parameters out of
/etc/sysctl.conf follow:

kernel.shmall = 1352914698
kernel.shmmax = 1352914698

And here's what I guess are the pertinent data from the postgresql.conf
file:

sort_mem = 65536
vacuum_mem = 262144
effective_cache_size = 196608
shared_buffers = 131072
max_fsm_relations = 200
max_fsm_pages = 350000
wal_buffers = 32

We've seen the problem with vacuum_mem = 65536 also.

--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc. http://www.nexcerpt.com
...Nexcerpt... Extend your Expertise