| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | 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:04:13 |
| Message-ID: | 14228.1061485453@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2003-08-21 17:08:47 | Re: [HACKERS] Can't find thread on Linux memory overcommit |
| Previous Message | Josh Berkus | 2003-08-21 16:19:48 | Re: [HACKERS] Can't find thread on Linux memory overcommit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2003-08-21 17:08:47 | Re: [HACKERS] Can't find thread on Linux memory overcommit |
| Previous Message | Josh Berkus | 2003-08-21 16:19:48 | Re: [HACKERS] Can't find thread on Linux memory overcommit |