| From: | Kurt Roeckx <Q(at)ping(dot)be> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:11:39 |
| Message-ID: | 20030821171139.GA11389@ping.be |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Thu, Aug 21, 2003 at 01:04:13PM -0400, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > Well, sadly, the reason I posted is that I (apparently) had a client's
> > database fatally corrupted by this problem.
>
> "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?
Kurt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-08-21 17:13:26 | Re: Can't find thread on Linux memory overcommit |
| Previous Message | Josh Berkus | 2003-08-21 17:09:27 | Re: Can't find thread on Linux memory overcommit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-08-21 17:13:26 | Re: Can't find thread on Linux memory overcommit |
| Previous Message | Josh Berkus | 2003-08-21 17:09:27 | Re: Can't find thread on Linux memory overcommit |