| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
| Date: | 2010-12-19 16:28:03 |
| Message-ID: | AANLkTim5fRWcLGr6Rmtf1JWyig9TpwvBDSpD+cWqDsoZ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Dec 19, 2010 at 11:07 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I agree that having the crash dump code know anything specific about the
> contents of shared memory is a nonstarter --- far too fragile. But
> perhaps we could have some simple rule based only on what the kernel
> knows about the shmem block, like "dump shmem if it's no more than 1GB".
Not sure what knobs we have available, but would there be any value in
trying to dump the FIRST 1GB?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-12-19 16:34:13 | Re: Extensions, patch v20 (bitrot fixes) |
| Previous Message | Tom Lane | 2010-12-19 16:26:11 | Re: keeping a timestamp of the last stats reset (for a db, table and function) |