| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kurt Roeckx <Q(at)ping(dot)be> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Jon Jensen <jon(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Can't find thread on Linux memory overcommit |
| Date: | 2003-08-21 17:14:51 |
| Message-ID: | 14777.1061486091@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Kurt Roeckx <Q(at)ping(dot)be> writes:
> On Thu, Aug 21, 2003 at 01:04:13PM -0400, Tom Lane wrote:
>> "Fatally corrupted"? That should not happen --- at worst, an OOM kill
>> should lose your current sessions. We need more details.
> Even if it kills the postmaster?
Then you'd have to start a new postmaster. But it still shouldn't
corrupt anything.
(Since the postmaster has small and essentially constant memory usage,
it's a pretty improbable target for the OOM killer, anyway.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2003-08-21 17:42:30 | Re: Can't find thread on Linux memory overcommit |
| Previous Message | Josh Berkus | 2003-08-21 17:13:26 | Re: Can't find thread on Linux memory overcommit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-08-21 17:28:53 | Re: "SELECT IN" Still Broken in 7.4b |
| Previous Message | Josh Berkus | 2003-08-21 17:13:26 | Re: Can't find thread on Linux memory overcommit |