| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: probs with postgres |
| Date: | 2003-03-21 05:59:57 |
| Message-ID: | 10306.1048226397@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> 5. We have been having load and stability problems with our Postgres since
> we released a massive upgrade to our website. We did actually have one time
> when Postgres crashed and the whole server rebooted when we got a bunch of
> these:
> Mar 20 09:25:54 serendipity /kernel: pmap_collect: collecting pv entries --
> suggest increasing PMAP_SHPGPERPROC
[blink...] Perhaps you should be asking hard questions about the
stability of your kernel. What are you running, anyway?
This is not to say that Postgres might not have its own problems --- but
Postgres is an unprivileged process. If your kernel is crashing, it is
not Postgres that's broken.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-03-21 06:07:12 | Re: A bad behavior under autocommit off mode |
| Previous Message | Shridhar Daithankar<shridhar_daithankar@persistent.co.in> | 2003-03-21 05:57:53 | Re: Extracting time from timestamp |