always forced restart after status 139?

Hi all,

We are using Postgres 7.1 on RedHat Linux 7.1.

When calling a C function in a shared library (*.so), if you get a
segmentation fault (status 139), the log indicates that the database will
shut down and then restart in a few seconds.

My question is, does this always have to happen? Is postgres capable of
just logging the seg fault, but not affecting all the users on the database
by restarting?

Thanks,

Jason
jwilliams(at)wc-group(dot)com
__________________________________________________
Expand your wireless world with Arkdom PLUS
http://www.arkdom.com/