| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <newsreader(at)mediaone(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: FATAL 1 |
| Date: | 2001-08-10 14:50:03 |
| Message-ID: | Pine.LNX.4.30.0108101646430.703-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane writes:
> Probably. If your *postmaster* is running out of memory then you have
> some serious problems. (But: we have had memory-leak problems in the
> past in certain authentication paths. What PG version are you running,
> anyway?)
I think the behaviour is that if the system as a whole runs out of memory
(physical + swap or whatever) the kernel randomly kills processes to make
room. So a disappearing postmaster is not necessarily a sign of a fault
on PostgreSQL's part. I'm not sure how to configure the kernel in this
area, I just recall the discussion on the kernel mailing list about
whether the init process would be allowed to be randomly killed as well.
(I kid you not.)
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Travis Bauer | 2001-08-10 14:56:47 | PL/Perl on Solaris |
| Previous Message | Dave Cramer | 2001-08-10 14:38:53 | Just Sports Usa, Supply Chain Management |