I have my server set up with one production postgres installation, and each
user can have their own database for their own use (usually web-related).
There are a limited number of trusted users, and I recently allowed one to
define a C-language stored procedure. Unfortunately, I *think* this causes
the users database process to crash, roughly once a week (probably a memory
leak).
The result of this is that *all* postmaster processes die, which is
actually a problem for the other users. Now the simple solution is to have
one PG installation per user (or at least one PGDATA directory), but that
does seem a little inefficient.
I'd be interested to know the reason for killing the other backends; it
does basically mean that each database has to have it's own PG installation
if you want reliability.
Would there be any potential to avoid these (possibly) unnecessary deaths?
Does the WAL and recovery process have any influence here?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
